Error when loading global enumerations using load from file

Forum|Forum|2 years ago
November 21, 2023
2 replies
3823 views

Hello,

I am trying to load global enumerations from windchill 11.1 to windchill 12.0 using Load from file command. However, I am facing an an uniqueness exception in doing so. The windchill version for the target system is 12.0.2.15 with CPS15 installed. I have attached the log file containing the error. Kindly provide any suggestions on how to resolve this,

Command used:-

windchill --javaargs="-Dwt.auth.trustedAuth.username=wcadmin" wt.load.LoadFromFile -d /appl/ptc/builds/SCF_Lufkin_Build/loadFiles/sic/GlobalEnumerations/Global_Enum_All_0.xml

Thanks,

Ramsha

1_error.txt

Upgrade_Migration

HelesicPetr

22-Sapphire II

Hi @RK_10805837

Your source file contains some global enum values that are not unique as it is needed in the database.

You need to find what value is not unique.

PetrH

R

RK_10805837

Author

10-Marble

Hi @HelesicPetr ,

A colleague of mine has used the same source file to load into his local windchill and it seems to be working fine for him. I guess this is a database issue not related to the loader file. Could you please provide any hints on how to resolve that?

Thanks again,

Ramsha

HelesicPetr

22-Sapphire II

Hi @RK_10805837

It is possible.

The point is that the system can already contains some values that has to be unique and yours are just duplicated.

One record is not unique and you need to find what it is.

Go to database and check the table LWCLocalizablePropertyValue

select * from wcuser.LWCLocalizablePropertyValue

compare the values to your file

add a where condition

select * from wcuser.LWCLocalizablePropertyValue
where idA2A2='5422'

also you can divide your file and try to load one enumeration by one , and thanks that you can find what is wrong.

PetrH

PS> if you can share a source file, it can be useful.

Fadel

23-Emerald I

Windchill complains about below entry in DB

LWCLocalizablePropertyValue:5422

you can import the attached qml on the target system and run it with the given id 5422, it should then give better sight in the problematic entry in DB