Pattern Model Bug Workaround – Reusing Deleted Names
- April 12th, 2011
- Posted in Universal Configuration Management Database
- Write comment
There exists a bug that does not allow you to create a new model with a name that was previously used and in deleted pattern model. What we observe is if the model is deleted, the TQL remains. If the TQL is deleted first, both the model and TQL are deleted. However, in either case, a related job remains in the Scheduler that will as a result re-create the model/tql on its next scheduled run.
The real issue is that the current "delete function" does not actually delete a pattern model name/ucmdb_id value from the database. As of 9.03, there is only the following workaround:
1) In SQL Server Management 2008, run the following Query:
select CMDB_ID, A_SCHEDULER_JOBNAME from CDM_SCHEDULER_JOB_1
The output correlates the pattern model name to a hex value. With the hex value, the JMX console can be used to delete the object.
Note: When copying the hex from the DB query, remove the "0x", otherwise the JMX console will not recognize the hex value.
2) Go to JMX console [http://:8080/jmx-console], and login with credentials (default: sysadmin/sysadmin).
3) Click on UCMDB:service=ModelServices – under UCMDB, and then Click on removeCMDBObject.
4) Enter the following:
customerID: 1
objectID: <your hex value>
5) Click Invoke. Done.
UPDATE: 04-19-2011
This Bug will be addressed in the uCMDB 9.03, CUP2 patch, slated for release by June, 2011.
No comments yet.