Problem modifying DPTs used as REF

Discussions about product bugs & problems!
Note: This is no replacement for the Official ETM Support!
4 posts • Page 1 of 1
nmnogueira
Posts:125
Joined: Thu May 05, 2011 12:59 pm

Problem modifying DPTs used as REF

Post by nmnogueira »

Hi,

I am having two different problems trying to update DPTs used as reference in another DPTs. What I am trying to do is to add a new element of type bool to the DPT.
Notice that these two problems appear in different DPTs. Each DPT always shows the same behaviour.

Problem 1
When I try to change, I get the following error:

Code: Select all

WCCILdata    (0), 2017.09.19 10:41:43.266, IMPL, SEVERE,     54, Unexpected state, PersDpIdentification, handleManipTypeChangeMsg, changeType unmoeglich, type container returned 2
WCCILdata    (0), 2017.09.19 10:41:43.266, SYS,  INFO,      119, Last error repeated 940 times.
WCCILdata    (0), 2017.09.19 10:41:43.266, PARAM,SEVERE,     54, Unexpected state, DataManager, handleManipDpTypeChangeMsg, Type change failed
Problem 2
When I try to change, the change is done correctly but the changes are not propagated to the DPTs which use this DPTs as a reference.


Any ideas?

leoknipp
Posts:2928
Joined: Tue Aug 24, 2010 7:28 pm

Re: Problem modifying DPTs used as REF

Post by leoknipp »

Maybe changing the datapoint type is not possible due to an inconsistency in the database.
How are you changing the datapoint type (PARA module, ASCII manager, ...)?

Do you already have historical data for the datapoints which belong to the type which need to be changed?
Would it be possible to loose the historical data?

Best Regards
Leopold Knipp
Senior Support Specialist

nmnogueira
Posts:125
Joined: Thu May 05, 2011 12:59 pm

Re: Problem modifying DPTs used as REF

Post by nmnogueira »

I'm changing in PARA.

I do have historical data but it's not an issue to loose that data.

leoknipp
Posts:2928
Joined: Tue Aug 24, 2010 7:28 pm

Re: Problem modifying DPTs used as REF

Post by leoknipp »

Just for information to all users in the forum.
The issue was analyzed by the support team. I could not find an easy solution to extend or modify the dp types where the problem occured as the dp type was used in many other dp types as type reference.
As loosing historical data was not a problem in that project a complete new database was created.

In other cases maybe another solution can be used, e.g. deleting only the corrupted dp type and recreating again.
This is only possible if it is not used as type reference. Otherwise you have to change all type references and delete the reference information to the corrupted dp type.

Best Regards
Senior Support Specialist
Leopold Knipp

4 posts • Page 1 of 1