Import Data Point Type Changes

[pablo.chamorro]

Hello,

We have doubts about how import Data Point Type changes, like can be adding a new Data Point Element.

When we make a DPTs change on local (Developer computer), before import this changes we delete the now obsolet DPTs on the Development Server using dp functions in a script. Then we import the dplist with the new DPTs.

Doing that, the Development Server somehow ends completly busied and we need to restart it. There our doubts, are we missing something? Maybe we need to do something before delete a DPTs, like deactive all DPE _addess?

We think that the problem is on our way to delete the DPTs. Some relationship keeps on memory and it makes server ends completly busied.

We use 3.17 P007.

Thanks.

[leoknipp]

Possibly there are some dpQueryConnects running in your system and therefore the system load is very high when doing modifications in the data model.
If the problem occurs please check which WinCC OA process is using a lot of CPU time.
With the report flag "-report query" for the Event Manager you can get the information which query connects are running.

If you only want to add new dp elements to an existing DP type there is no need delete all the information. You just can modify the DP type.

Best Regards
Leopold Knipp
Senior Support Specialist

[pablo.chamorro]

Hi leoknipp,

Having a look on the Event Manager Connections panel and checking the Ascii log we found some troubles. We understand all except one.

In a while we change some DPEs (bool, int, whatever ..) to embed DP-Type. After this change, some times, when we make an import that contains those DPEs, ascii prints this message:

WCCOAascii (1), 2021.03.12 09: 59: 57.403, IMPL, SEVERE, 54, Unexpected state, PersDpIdentification, handleManipDpAliasMsg, identification returned "alias exists"

It only happens with DPEs that was changed to embed DP-Type. And when we search were this alias are, we see this:

Unexpected state, dpIdentifier, formatValue, could not convert DpIdentifier to string: (Type: 0 Sys: 1 Dp: 12152 El: 28: ..)

What it means? It seems like DPs are not deleted at all from the system. If it happens with aliases, it means that _address and the rest of configs that we belived deleted keeps working without us knowing?

[leoknipp]

We know about a problem that sometimes alias information is not deleted if embedded DP types are used and datapoint and/or elements are deleted.
Currently there is no solution for it available.
To avoid the problem you can delete all the alias information for the datapoints or elements which shall be deleted.

Best Regards
Leopold Knipp
Senior Support Specialist