We looked through our cmdb.dal.log and found multiple occurences of this error:
2013-08-12 19:01:16,548 [UCMDB - global framework scheduler] ERROR Failed to execute command [CmdbDalAddCPCommand] time [15108 ms] customer ID [-2147483648] operation stack [N/A]
com.mercury.topaz.cmdb.server.manage.dal.CmdbDalException: [ErrorCode [-2147483648] undefined error code]
Error adding Content Pack Version [-1.0.0] to database
Caused by: java.lang.RuntimeException: Content Pack Version [-1.0.0] already exists in the database.
... 15 more
I then checked the CP versions and found that -1.0.0 was present in the list. I stopped the service, deleted the rogue content pack from the server and restarted. Invoking the JMX mbean to check the CP versions shows that -1.0.0 is no longer there, but cmdb.dal.log is still throwing these errors. I checked the Server content packs directory and found that CP -1.0.0 was rewritten. I also cleaned and restarted the probe too, to no effect.
Checking the contents of CP -1.0.0 reveals that it is the parent zip for a content pack update, likely inserted by mistake during an upgrade.
Any suggestions on where this rouge CP -1.0.0 may still exist in the DB or why cmdb keeps rewriting the file?
We have a customer who installed the wrong content pack (CP 12 Update 14) on 10.01 because the wrong zip file was uploaded to theit FTP server (it should have been CP12 Update 4). They run into an error during an installation and when troubleshooting I realized this version should not have been installed on 10.01. We are planning to remove that and install the correct CP, CP 12 Update 4 but in the release note for CP 12 Update 14, there is a note that talks about rolling back from this is NOT supported. Any idea what the reccomendation is if we can't roll back? Can we follow the same step of removing stopping the service, removing the file from the file system, deleting it from the DB and then restart to deploy the correct version or does this require backing up the database?
It is a production system so we have a change scheduled for Monday April the 13. I would really appreciate it if you can get back to me on this as soon as possible. I have attached screenshot of the error and CP versions we have.