
steffen1 asked a question.
Just for other people and Flexera as a hint,
trying to update FNMS on Prem 2022R2 to 2023R1 db migration on FNMSInventory run into an error for me:
...Running 'im-migr1920-migpost.sql...
There was an error while attempting to run 'im-migr1920-migpost.sql'.
Violation of PRIMARY KEY constraint 'PK_HardwareClass'. Cannot insert duplicate key in object 'dbo.HardwareClass'. The duplicate key value is (MGS_IBMz_Layer).
Migration step 10004, part of action set "Adding IBM z/VM AND zKVM vm types"
The Class 'MGS_IBMz_Layer' was alread present in 2022R2 with diffrent Values in 'HardwareClassID' and 'SuperClassID' can be verifiey by:
USE FNMSInventory
SELECT * FROM dbo.HardwareClass
-- WHERE HardwareClassID = 8001 --in2023R1 '8001' is expected; in 2022R2 it was on my system '10018'
WHERE CLASS = 'MGS_IBMz_Layer'
WorkAround: simply remove the old entry from 2022R2 - it will be re-created correctly - and kick off db migration again
USE FNMSInventory
delete dbo.HardwareClass
WHERE CLASS = 'MGS_IBMz_Layer'
NearBy:
looks to me as a specific bug only applying 2022r2 -> 2023r1 because in 2022r1 first "IBMz" stuff was introduces but not offically supported
greetings
Steffen
Thanks Chris,
Thanks Aamer,
both of you are right we deployed the 2022R2 Agent Linux on zOS, which is part of the offical distribution package onto about 20-30 zOS VM Guests with strange effects (25 guests merging into about 2-3 ComplianceComputer un the GUI). We hope that this isse will no longer exist using 2023R1 Application Server and 2023R1 Agents. (Problem is still there with 2023R1 ApplicationServer and 2022R2 Agent)
Once we updated the Guest Agents we will see and I will post the status.
Greetings - Steffen