Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

UCMDB Support Tip: How to Discover Reconciliation Problems?

The following problems in the UCMDB may indicate a reconciliation issue:  


1. Data that should have been added\updated\removed was unaffected.

2. CIs that you would have expected to be merged together remained separate

3. A CI is “missing”, and perhaps it has been merged with another CI


How can you be certain you're dealing with a reconciliation issue? Some cases are easily identified as a reconciliation problem because the error log (and the reconciliation logs) will show an exception that originated in the reconciliation engine (for example, “not enough reconciliation data”). Some cases are not as easily identified, since no exception is thrown during the process. For example, if two CIs were merged together, even though they shouldn’t have, obviously the data in operation finished successfully.


This requires more investigation:


1. Identify the problematic operation

         What data was sent in the bulk?

         What was the data-in operation?

         What data was present in the UCMDB?

For example, an answer to these questions may be: I ran the discovery job “Host by SNMP” on the IP X.X.X.X, and  the   IP already had a node connected to it.

2. Open the reconciliation logs for debug.

3. Rerun the problematic operation.

4. When the problem occurs it is advised to copy the logs to a new location, since the logs files are cyclic, so the relevant data for the problem may be overwritten.

5. Open the reconciliation audit log and identify the operation or operations that may have caused the problem. Save the operation IDs of these operations.

6. Usually, the most useful and comprehensive log is the cmdb.reconciliation.log. Find the operation IDs from the previous step. This information (maybe combined with the ignored logs or one of the other logs) should be enough for most reconciliation problems. More often than not, you may find out that the reconciliation did work properly and the bulk’s data was incorrect or that the data should have been merged because of some condition in the CI’s identification rule.

“HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”

Click the KUDOS star on the left to say 'Thanks'
Labels (1)
Tags (1)
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.