This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

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.

Before you begin

Run cmdbdiag tool and provide log on 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.

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.

Related topics

Using the CDMChecker tool

Verifying your data model using the cmdbdiag program

Was this page helpful? Yes No Submitting... Thank you

Comments