Absent Member.. Absent Member..
Absent Member..

UCMDB Support Tip: Reconciliation Few Common Issues

1.   When trying to add, update or remove data (using UI, discovery, enrichment) and the operation fails with message “Not enough reconciliation data” error message

Problem: The error.log, cmdb.reconciliation.audit.log or cmdb.reconciliation.log contains the error “Not enough reconciliation data”. CI did not identify to itself in bulk”.

If trying to manipulate UCMDB using the SDK an appropriate exception with the same message will be thrown.

If trying to add\update data using the UI, an appropriate error message with the same message is displayed.

When one get this message no data from the bulk is added\updated\removed from the UCMDB.

Cause: There is at least one CI in the data in bulk that is missing its reconciliation data, therefore could not have been identified and processed. There are some attributes or connected CIs that are needed for identification, but are not present in the bulk (neither as a “for update” nor as a “referenced” object). Remember that for a connected CI identification one must have the same type of link, direction, end type and in some cases one or more attributes on the connected CI. For a lot of attributes an “empty value” is not a valid value for reconciliation purposes. So, make sure is not relying on such an attribute for the failing bulk’s identification.

Workaround: Fix the data in the bulk so all of the CIs will have their identification data present. After that, send the bulk again to a data in operation.


2.   Admin can’t add a new Node to the UCMDB

Problem: The identification rule for a node is too complicated.

Cause: This problem is easily identified, because one most likely get the message “Not enough reconciliation data” (as also seen in issue 1).

Workaround: The node’s identification rule is quite complicated, and a lot of times it’s difficult to understand why a new node is not added or is added but merged to another.

A few guidelines:

    1. Make sure at least one condition from the “identification” section of the identification rule exists (for example “name” or “snmp_sys_name”.

    2. The node may be identified using only connected CIs (IP Addresses and\or interfaces). Note that each of these requires specific attributes (like mac_address for interface), and those may not exist in the connected CI.


3.    UCMDB is in authorized state and cannot add any data

Problem: When UCMDB is in an authorized state no data may be added using the UI.

Cause: UCMDB is in an authorized state.

Workaround: One may not alter the data in an authorized state. Revert to the actual state is needed.


4.    Host resource was ignored (or any other CI with a container)

Problem: In the data flow management UI or the ignored log, can see that a host resource (like a disk,  CPU and etc.) was ignored.

Cause: The ignored CI’s root container was ignored, as a result and CI that has it as its root container is ignored as well. A container is not necessarily the ID in the root_container attribute. A container may be specified by an attribute with the CONTAINED_BY qualifier.

Workaround: Find the CI’s root container using the ignored log (or if the logs are opened for debug the cmdb.reconciliation.log). Still in the ignored log, find the reason for why the root container was ignored and act accordingly.

"HP Support
If you find 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.