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 Helix CMDB installation.
Run the CDMChecker utility to:
- Detect invalid customization
- Detect CDM corruption
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
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>
To compare a CDM on a sever specified by <server> with another CDM in the XML file specified by
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.
The details about cdmchecker commands are given in the following table:
|Command name||Action performed|
Exports the CDM to an .xml file specified by the
Compares the target CDM with the CDM in the xml file specified by
Compares the CMDB Class meta data with the underlying AR forms and points out the differences. This is the
|Determines if there are classes and attributes in pending state.|
Finds missing fields on AR form required for CMDB attribute.
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.
On an 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
You must copy all the libraries available in cmdb/server/bin to sdk/sdk64 using the following command:
yum install <filename>