This documentation supports the 20.08 version of BMC CMDB, which is available only to BMC Helix subscribers (SaaS).

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

Troubleshooting a failed data model change

If the class or the attribute that you modified in the Class Manager displays a Change Pending icon or if its status changes to Error, your changes might not have been saved to your data model.

  1. In the Class Manager, click Table View.
  2. Click the Status column to sort by Status.
  • If classes have a status of Change Pending, wait until the synchronization process is complete.
  • For any classes which display a status of Error, place the cursor on the Status tab to view the error message. The error message typically describes the reason for the failure.

To view more information on error messages, see Error messages.

To verify the underlying Remedy AR System data structures

  1. Start the Maintenance Tool.
  2. Perform a health check.
  3. Verify whether the output for CDMChecker reports the status as Successful.

If necessary, collect more detailed logs to capture the failure by enabling CMDB server-side logging as described in Enabling API and web services logs.

To perform additional diagnostics

  1. Open the Server Information form in the mid tier from the following location:
    AR System Administration AR System Administration Console >  System > General > Server Information.
  2. Open the Log Files tab.
  3. Enable API, SQL, and Filter logging.
  4. Recreate the failure.
  5. Disable the logs.
  6. Start the Maintenance Tool and click Zip All Logs. This step captures both AR System and BMC CMDB Logs.
  7. Start Remedy AR System Maintenance Tool on the system running mid tier and click Zip All Logs.
Was this page helpful? Yes No Submitting... Thank you

Comments