Verifying your data model manually
Perform the following steps to verify that the class definitions in your data model are correct.
Before you begin
cmdbdiag tool and provide log on credentials.
cmdbdiag logs on, it tells you that the Configuration Management Database (CMDB) is responding to BMC Atrium CMDB API calls. Alternatively, run the Health Check from BMC Atrium Core Maintenance Tool.
If you receive an
AR 91 RPC call failed error, verify that
cmdbEngine is running. This error might also occur if the class definitions in the your data model are incorrect.
To manually verify your data model
- Examine the arerror.log and cmdbengdebug.log files for any errors about starting the
Search for the string
cmdbEngineto find errors. When
cmdbEngineis started, it validates the class definitions. The following example shows the error message that you might view in arerror.log:
Mon Dec 11 16:10:18 2006 390600 : The specified super class with given classId is not found. : Class ID: OB005056C00008PlV3RQU3oZAAHO8C, Super Class ID: OB005056C00008F1V3RQd#IYAAD90C (ARERR 120132)
For more information about arerror.log, see AR System server logging. For more information about cmdbengdebug.log, see BMC Atrium Core Console server-side logging.
- Run the
cdmcheckercommand line executable in the same directory as
cmdbdriver, with the