Check reconciliation to BMC Atrium CMDB golden dataset (BMC.ASSET)

Verify that configuration items (CIs) are merged to the BMC.ASSET dataset. This step confirms that the BMC Server Automation server information is reconciled into the golden dataset used by BMC Atrium CMDB applications.

Task

Products involved

Description and reference

Verify that the Reconciliation Job ran after all the BMC Server Automation data was populated into the BMC.IMPORT.BL dataset.

BMC Atrium Core Console

From the BMC Atrium Core Console, access Reconciliation. Select the BMC Server Automation Reconciliation Job and check when it ran and whether it completed.

For more information, see the following topics in the BMC Atrium Core Troubleshooting Guide (available here):

  • "Reconciliation Engine startup issues"
  • "Job issues"

Check if errors occurred during reconciliation, and identify the error numbers.

BMC Atrium Core Console

The Identification activity in the Reconciliation Job sets the value of ReconciliationIdentity to a non-zero value for each CI and relationship. If errors occurred during identification, the CIs did not participate in the merge activity, and the same CIs will attempt to be identified during the next job run.

Reconciliation logs are enabled at the ERROR level by default, so if the job run reports errors, you can examine the logs to identify how many different error numbers occurred. Typically there are many errors, but just a few causes of those errors.

Best practice: Identify one example Computer System to investigate for each error. Then identify and resolve the cause of the error.

For more information, see the following topics in the BMC Atrium Core Troubleshooting Guide (available here):

  • "Reconciliation Engine logging"
  • "Troubleshooting logging issues" (describes issues with enabling reconciliation logs)

Characterize issues in reconciliation.

BMC Atrium Core Console

Some issues result in an error message that occurs during reconciliation. Other issues lead to unexpected results in the data in the BMC.ASSET dataset, but do not have a corresponding error messages. Procedures for investigating most of these types of issues are provided either in the BMC Atrium Core Troubleshooting Guide (available here), or in the BMC Knowledge Base. For example:

  • Unidentified CIs - see "Troubleshooting unidentified instances issue" 
  • Duplicate CIs - see "Troubleshooting multiple CI matches in BMC.Asset"
  • Multiple Match error during identification - see "Resolving multiple CI matches in the source dataset"
  • Missing endpoints - see "Missing endpoints during the Merge activity"
  • Performance Issues in Reconciliation - see "Performance Issues"
  • Missing CIs in the CMDB – Search the BMC Knowledge Base.
  • Troubleshooting data inconsistencies in CMDB – Search the BMC Knowledge Base.

Enable debug logging

BMC Atrium Core Console

If you need more detailed information about the errors, configure the reconciliation log type to "Debug" mode.

To enable reconciliation logging:

  1. Access the Atrium Core Console.
  2. Launch the Reconciliation applet.
  3. Click the Edit Server Configuration icon.
  4. Change the Logging Level to Debug and click Save.

For more information about how to do this, "Reconciliation Engine logging" in the BMC Atrium Core Troubleshooting Guide, which is available here.

If the error numbers are reported by BMC Atrium Core, BMC Remedy AR System, or a BMC Remedy ITSM application, enable API, SQL, Filter, and Plug-In logging to capture more detail about the process that leads to the error.

To enable BMC Remedy AR System Filter, API, SQL, and Plug-In logs:

  1. Access BMC Remedy AR System by using the following URL in a browser:
    http://<midTierServer>:<port>/arsys/forms/<ARserverName>
  2. Log on.
  3. Click the AR System Administration Console link.
  4. Navigate in the tree: System > General > Server Information.
  5. Select the Log Files page.
  6. Select the checkboxes for API, SQL, Filter, and Plug-In. Verify each writes to a file, and note the file name and location. Select the option for Plug-In Log, and set Log Level to All. Set Maximum Log-File Size to 0 (zero) for unlimited.
  7. Click Apply to enable the logs. The changes happen immediately.

Collect standard diagnostics and analyze logs

BMC Atrium Core Console

Launch AtriumCoreMaintenanceTool and click Zip All Logs to collect the logs and configuration for BMC Atrium Core. For more information, see "How to prepare log files for BMC Customer Support" in the BMC Atrium Core Installation Guide, which is available here.

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

Comments