Verifying your data model manually
Perform the following steps to verify that the class definitions in your data model are correct.
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
cmdbdiagand provide logon credentials.
cmdbdiaglogs 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.
cdmchecker -x <filename> -u <username> -p <password> -s <server> -t <tcp port>
Exports the CDM to an .xml file specified by the
<filename>. The XML format is the format used by the regular CMDB Export API.
cdmchecker -c <filename> -u <username> -p <password> -s <server> -t <tcp port>
Compares the target CDM with the CDM in the xml file specified by
<filename>. This option is useful to determine the customizations in the environment. Run
CDMChecker with the
-x option on a QA box and use this file for the
-c option in the problematic environment.
CDMChecker points out the class differences, the new attributes, the changed attributes, and so on.
cdmchecker -m -u <username> -p <password> -s <server> -t <tcp port>
Compares the CMDB Class meta data with the underlying AR forms and points out the differences. This is the
CDMChecker validation performed by the Health Check and written to missing_fields.log.
cdmchecker -g -u <username> -p <password> -s <server> -t <tcp port>
This option determines if there are classes and attributes in pending state.