This documentation applies to the 8.1 version of BMC Atrium Core, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

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

  1. Examine the arerror.log and cmdbengdebug.log files for any errors about starting the cmdbEngine.
    Search for the string cmdbEngine to find errors. When cmdbEngine is 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.
  2. Run the CDMChecker command line executable in the same directory as cmdbdriver, with the -g parameter.
  3. Run cmdbdiag and provide logon credentials.

    If 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.

Note

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 commands

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.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments

  1. Ketan Magdum

    We have one more option as "cdmchecker -a -u [username] -p [password] -s [server] -t [tcp port] -o[errorfilename]"

    Jul 22, 2013 04:17
    1. Vaijayanti Nerkar

      What does this option do? Please explain so we can add immediately.

      Jul 22, 2013 04:26