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 using the cmdbdiag program

The cmdbdiag program is a command-line tool, which is located in the cmdb\server64 directory of your BMC Atrium Core installation. This program allows you to check for any invalid data in BMC Atrium Configuration Management Database (BMC Atrium CMDB) and correct it.

Working with the Data Integrity Checker option

The Data Integrity Checker validates BMC Atrium CMDB for the various issues based on the menu option you choose. If the Data Integrity Checker finds invalid data, it creates a report that contains information about the invalid relationship instances and datasets.

To start the cmdbdiag program

When you launch cmdbdiag, provide your BMC Remedy AR System logon credentials for the computer hosting BMC Atrium Core.

  1. Navigate to the appropriate location where you copied the cmdbdiag program and perform the following step:
    • On Windows, double-click cmdbdiag.exe.
    • On UNIX, type cmdbdiag.
  2. From the initial screen for the cmdbdiag program, log on to the AR System server. The cmdbdiag program Main Menu appears.

To troubleshoot invalid relationships

Check for invalid relationships — relationship instances that point to nonexistent Configuration Item (CI) instances or relationships that contain incorrect endpoint information, such as incorrect dataset ID or class ID.

  1. Start the cmdbdiag program.
  2. At the Main Menu prompt, type 1.
  3. At the Data Integrity Checker prompt, type 1.
  4. At the All datasets [y, n] prompt, perform the appropriate action:
    • To view invalid relationships for all datasets, type y.
    • To view invalid relationships for a specific dataset, press Enter and provide a dataset ID.
  5. Enter a name for the output file, or press Enter to accept the default file name.
    If you enter a file name manually, specify an absolute path for the file (for example, C:\DIC_Invalid_Relationships.txt). Otherwise, the program saves the report file in the same directory as the cmdbdiag program.

To troubleshoot invalid dataset IDs

Check for invalid dataset IDs — Incorrect dataset IDs specified for CI and relationship instances. A dataset ID might be incorrect if it refers to:

  • A nonexisting dataset
  • Contains a value of 0 or NULL
  1. Start the cmdbdiag program.
  2. At the Main Menu prompt, type 1.
  3. At the Data Integrity Checker prompt, type 2.
  4. Specify a name for the output file or press Enter to accept the default file name.
    If you manually enter a name, you must specify an absolute path for the file (for example: C:\dataset_ids.txt ). Otherwise, the program saves the report file in the same directory as the cmdbdiag program.

To troubleshoot invalid CI relationships

Check for relationship cardinality issues — invalid relationships that are caused by a violated relationship cardinality, which occurs when a relationship between CI classes does not fall into one of the following categories:

  • One to one
  • One to many
  • Many to one
  1. Start the cmdbdiag program.
  2. At the Data Integrity Checker prompt, type 3.
  3. At the All datasets [y, n] prompt, perform the appropriate action:
    • To check for relationship cardinality issues for all datasets, type y.
    • To check for relationship cardinality issues for a specific dataset, press Enter and provide a dataset ID.
  4. Specify a name for the output file or press Enter to accept the default file name, test_cardinality.txt.
    If you manually enter a name, you must specify an absolute path for the file (for example: C:\DIC_Cardinality.txt ). Otherwise, the program saves the report file in the same directory as the cmdbdiag program.
  5. To exit the Data Integrity Checker option, type 4.
Was this page helpful? Yes No Submitting... Thank you

Comments