This documentation supports the 20.02 version of BMC CMDB.

To view an earlier version, select the version from the Product version menu.

Troubleshooting issues when using the CDMChecker tool

The CDMChecker program is a command-line tool, which is located in the cmdb\server64 directory of your BMC CMDB installation.

Run the CDMChecker utility to:

  • Detect invalid customization
  • Detect CDM corruption

Run the cdmchecker command line executable in the same directory as cmdbdriver, with the -g parameter. The XML format is the format used by the regular CMDB Export API. The XML format is the format used by the regular CMDB Export API.

CDMChecker example options

Export CDM

To export the CDM to an XML file specified by the <filename>, use the following:

cdmchecker -x <filename> -u <username> -p <password> -s <server> -t <tcp port>

Compare CDMs

To compare a CDM on a sever specified by <server> with another CDM in the XML file specified by <filename>:

cdmchecker -c <filename> -u <username> -p <password> -s <server> -t <tcp port>

This option is useful to determine the customization in your environment. Run the CDMChecker with the -x  option on a freshly installed environment without any customization and use that file for the -c option in the customized environment.  The CDMChecker points out the class differences, the new attributes, the changed attributes, and so on.



cdmchecker commands

The details about cdmchecker commands are given in the following table:


Command nameAction performed

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> -ch

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. The CDMChecker points out the class differences, the new attributes, the changed attributes, and so on. Additionally you can use the -ch option with the -c option to view the differences in classes, attributes characteristics and custom characteristics in the output. Using -ch  is optional.

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>

Determines if there are classes and attributes in pending state.

cdmchecker -a -u <username> -p <password> -s <server> -t <tcp port>

Finds missing fields on AR form required for CMDB attribute.

cdmchecker -y -u <username> -p <password> -s <server> -t <tcp port>

Checks if any overlay is created on CMDB class regular forms.


Error when running CDMChecker tool from sdk or sdk64 directory in Linux

When you run the CDMChecker tool on Linux with Oracle, the tool may display an error.

This error occurs when the dependent libraries are not present in the sdk/sdk64/bin folder.

Issue

On an Remedy AR System server on Linux and Oracle, if you go to to the path /data1/bmc/ARSystem/cmdb/sdk/bin, and set LD_LIBRARY_PATH to this location and then run the CDMchecker tool, you may see the following error:

./cdmchecker: error while loading shared libraries: libxerces-cbmc.so.28: cannot open shared object file: No such file or directory 

Resolution 

You must copy all the libraries available in cmdb/server/bin to sdk/sdk64 using the following command: yum install <filename>



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

Comments