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 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 Export API. The XML format is the format used by the regular Export API.
CDMChecker example options
Export CDM
To export the CDM to an XML file specified by the <filename>, use the following:
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:
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 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:
Resolution
You must copy all the libraries available in cmdb/server/bin to sdk/sdk64 using the following command: yum install <filename>