Root Cause 1: The CMDB account used to synchronize the CMDB does not have the permission to find the CI mentioned in the error message.
To confirm:
- Login to the CMDB with the account used by Discovery. It can be found in Administration > CMDB sync, Details tab.
- In the BMC_BaseElement form, search for 2-3 CIs mentioned in 120006 errors
- If any of these CIs can be found, this root cause can be eliminated
- If none the CIs can be found, re-execute the steps above with a CMDB user with full permissions such as the Demo user (with the initial settings). If all the CIs can be found with more CMDB permissions, the root cause is confirmed.
Solution: Configure Discovery to use a CMDB account compliant with this documented requirement (see "Username"). Note that accounts part of the "administrator" or "asset admin" group may not be compliant.
Root Cause 2: The CMDB ReconciliationEngine (RE) modified the attribute CMDBRowLevelSecurity of the CIs mentioned in the error message (and it keeps Discovery from finding them).
To confirm: Use the steps to confirm the root cause 1.
In the step 3, if only a part of the CIs affected by this issue can be found in the BMC_BaseElement form, this root cause is possible.
In the step 4, if the CIs that can only be found with more privileges had their CMDBRowLevelSecurity modified by RE, this root cause is possible.
Solution: Use the solution of the root cause 1.
Root Cause 3: The CI mentioned in the error was removed from the Discovery dataset (i.e. BMC.ADDM).
To confirm: Use the steps to confirm the root cause 1. In the step 4, if none of the CIs can be found, the root cause is confirmed.
Solution:
1-Resynchronize.
or
2- Delete the CMDB sync connection, recreate it, and resynchronize.
Root Cause 3: Data issue/corruption in the Discovery dataset in CMDB
To confirm: Use the steps to confirm the root cause 1. In the step 2. Check the ClassID in the BMC_BaseElement form and search again for the same CI in the form of the class specified in the ClassID. It is a subclass a subclass of BMC_BaseElement (like BMC_ComputerSystem, BMC_Cluster, BMC_Patch, ...). If the CI is only missing in the subclass (not in BMC_BaseElement), the root cause is confirmed.
Solution: In the case of helix cmdb, contact BMC Customer Support.
Otherwise (the CMDB is on prem):
1- delete the content of the cmdb affected by the issue and resynchronize
2- use the CMDB article below
BMC CMDB Suite Discovery-CMDB resync is failing : Instance not found (120006)
It's a procedure to delete the CIs affected by this issue (the one that are in BMC_BaseElement but not in the subclasses). resynchronize afterwards
Root Cause 4: The RE Purge deleted a CI (expected) and Discovery tried to undelete it (expected). This leaves an (expected) Error 120006 in the logs. This does not require any action, this is not an issue.
To confirm: If the error in bold below can be found in the logs, the root cause is confirmed.
transformer DEBUG log sample:
W33-140607540819712: 2018-11-05 13:52:53,027: cmdb_sync.sync: DEBUG: Relationship BMC_Dependency:NETWORKLINK (<id>==#BMC_Printer:Destination:<id>==#BMC_ComputerSystem:Source#BMC_Dependency) needs to be recreated
exporter DEBUG log sample:
com.tideway.integrations.cmdbsync.SyncTransaction: DEBUG: Updating BMC_Dependency key:<id>=#BMC_Printer:Destination:<id>=#BMC_ComputerSystem:Source#BMC_Dependency { ImpactDirection:10(Integer) HasImpact:5(Integer) MarkAsDeleted:0(Integer) Name:NETWORKLINK(String) }
[...]
com.tideway.integrations.cmdbsync.SyncTransaction: DEBUG: Update 1 instances...
[...]
ERROR (120006): Instanz wurde nicht gefunden.; <id>
[...]
com.tideway.integrations.cmdbsync.SyncTransaction: DEBUG: Inserting BMC_Dependency key:<id>==#BMC_Printer:Destination:<id>==#BMC_ComputerSystem:Source#BMC_Dependency
com.tideway.integrations.cmdbsync.SyncTransaction: DEBUG: Create 1 instances...
exporter INFO log sample:
RequestProcessor-30082: <timestamp>: com.tideway.integrations.cmdbsync.SyncProvider: INFO: Sync CIs: action = Re-create, count = 1, cred_id = d7e21b36d78fb4e9c9d69eab40247864
[...]
RequestProcessor-30082: <timestamp>: com.bmc.cmdb.api.CMDBAPILogger: FATAL: -CMDBSetInstance
ERROR (120006): Instance not found.; <id>
[....]
RequestProcessor-30082: <timestamp>: com.tideway.integrations.cmdbsync.SyncTransaction: WARN: Skip missing instance [
Instance Id=<id>
[
Namespace=BMC.CORE
ClassName=BMC_VirtualSystemEnabler
[...]