Reconciliation identification activities issue
If the Reconciliation Engine cannot find a match for an instance after applying all the identification rules, and if the instance is part of an Identification group that you did not specify to be auto-identified, the instance remains unidentified.
In such a case, you must manually identify the instance or modify the identification rules. For information about manually identifying data, see Manually identifying data by using the Reconciliation console.
To troubleshoot the unidentified instances issue
- Log in to the BMC Atrium Core Console and click Reconciliation.
For information about logging in to the console, see Navigating the interface.
- Click the History tab and verify that the specific job was successfully executed after the modified date of the configuration item (CI).
Reconciliation Engine jobs are typically named after the dataset that is used in the job. To determine the datasets that the job identifies, from the Administrative Information tab view the Identification activity.
- Verify that the Dataset ID of the CI matches one of the defined Dataset IDs.
- Verify that a qualification group is defined for the Identification activity.
- If a qualification group is defined, verify that the CI meets the qualification.
- Click Edit Server Configuration on the toolbar and configure the following settings for the Reconciliation Engine log:
Max Log File Size (kilobytes) = 20000
This setting enables you to zip the multiple log files for the same job and save them to another system in case the log files exceed 20 megabytes (MB).
Logging level = Debug
- Start the Reconciliation Engine Job again and wait for it to complete.
Search for the Instance ID of your test instance in the Job log to find the entry, such as the following entry:
[DETAILS] [TID: 000006]: Started identifying instance <class = BMC.CORE:BMC_ComputerSystem, instance id = OI 1F94C10B39834F35BFDB59EEC3791F96>
The DETAILS and TRACE entries appear only if you set the logging level to Debug.
For information about how to search the log file for the identifying instance entry, see Interpreting entries in the log file.