2 Replies Latest reply on Feb 11, 2019 9:11 AM by Duncan Grisby

    CMDB sync errors

    Nirmal Sharma
      Share:|

      Hi Experts,

      Discovery version 11.3

      CMDB version 9.1.03

       

      I have noticed sudden increase in sync errors. Below is the transcript of the errors picked using `cat  tw_cmdbsync_exporter.log| grep ERROR` command.

       

      ERROR (9713): The attempted bulk entry transaction failed due to an error in one of the individual operations.; Operation 1 in bulk transaction failed

      ERROR (120006): Instance not found.; OI-0946e4173f674bed877f61965ed5fc03

      ERROR (120006): Instance not found.; OI-0946e4173f674bed877f61965ed5fc03

      ERROR (9713): The attempted bulk entry transaction failed due to an error in one of the individual operations.; Operation 1 in bulk transaction failed

      ERROR (120006): Instance not found.; OI-95f294acdb9b44b3a26ff1f19a34ca07

      ERROR (120006): Instance not found.; OI-95f294acdb9b44b3a26ff1f19a34ca07

      ERROR (9713): The attempted bulk entry transaction failed due to an error in one of the individual operations.; Operation 1 in bulk transaction failed

      ERROR (120006): Instance not found.; OI-80ff3d5701674b5aa568671a8069a617

      ERROR (120006): Instance not found.; OI-80ff3d5701674b5aa568671a8069a617

      ERROR (9713): The attempted bulk entry transaction failed due to an error in one of the individual operations.; Operation 1 in bulk transaction failed

      ERROR (120006): Instance not found.; OI-fe38a028c3904c6fb6995976e3dde857

      ERROR (120006): Instance not found.; OI-fe38a028c3904c6fb6995976e3dde857

      ERROR (120006): Instance not found.; OI-ac2226e3e7774a14b509f3460307d524

      ERROR (9713): The attempted bulk entry transaction failed due to an error in one of the individual operations.; Operation 1 in bulk transaction failed

      ERROR (120006): Instance not found.; OI-09722569af1847669a8cff55b5525ac1

       

      However below is the long output from 1 instance of each different error from above.

       

      RequestProcessor-5: 2019-02-11 09:16:59,984: com.bmc.cmdb.api.CMDBAPILogger: FATAL: -CMDBSetInstance

      ERROR (120006): Instance not found.; OI-751b8ae7c5c6419face14fd2c0bf382b

              at com.bmc.cmdb.api.CMDBProxyJRpcBase.verifyStatus(Unknown Source)

              at com.bmc.cmdb.api.CMDBProxyJRpcBase.cmdbCall(Unknown Source)

              at com.bmc.cmdb.api.CMDBProxyJRpcBase.cmdbCall(Unknown Source)

              at com.bmc.cmdb.api.CMDBProxy.CMDBSetInstance(Unknown Source)

              at com.bmc.cmdb.api.CMDBInstance.update(Unknown Source)

              at com.tideway.integrations.cmdbsync.SyncTransaction.commit(SyncTransaction.java:253)

              at com.tideway.integrations.cmdbsync.SyncProvider.syncInstances(SyncProvider.java:467)

              at com.tideway.integrations.cmdbsync.SyncProvider.syncRels(SyncProvider.java:422)

              at CMDBSyncCORBA.GraphSyncPOA._invoke(GraphSyncPOA.java:182)

              at org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:297)

              at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:591)

              at org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:734)

      RequestProcessor-5: 2019-02-11 09:22:42,059: com.bmc.cmdb.api.CMDBAPILogger: FATAL: -CMDBEndBulkEntryTransaction

      ERROR (9713): The attempted bulk entry transaction failed due to an error in one of the individual operations.; Operation 1 in bulk transaction failed

      ERROR (120006): Instance not found.; OI-444b510beb7e47f69b5db9906c5e6975

              at com.bmc.cmdb.api.CMDBProxyJRpcBase.verifyStatus(Unknown Source)

              at com.bmc.cmdb.api.CMDBProxyJRpcBase.cmdbCall(Unknown Source)

              at com.bmc.cmdb.api.CMDBProxyJRpcBase.cmdbCall(Unknown Source)

              at com.bmc.cmdb.api.CMDBProxy.CMDBEndBulkEntryTransaction(Unknown Source)

              at com.bmc.cmdb.api.CMDBProxy.CMDBSetMultipleInstances(Unknown Source)

              at com.bmc.cmdb.api.CMDBUtil.CMDBSetMultipleInstances(Unknown Source)

              at com.tideway.integrations.cmdbsync.SyncTransaction.commit(SyncTransaction.java:244)

              at com.tideway.integrations.cmdbsync.SyncProvider.syncInstances(SyncProvider.java:467)

              at com.tideway.integrations.cmdbsync.SyncProvider.syncRels(SyncProvider.java:422)

              at CMDBSyncCORBA.GraphSyncPOA._invoke(GraphSyncPOA.java:182)

              at org.jacorb.poa.RequestProcessor.invokeOperation(RequestProcessor.java:297)

              at org.jacorb.poa.RequestProcessor.process(RequestProcessor.java:591)

              at org.jacorb.poa.RequestProcessor.run(RequestProcessor.java:734)

       

      Please help.

        • 1. Re: CMDB sync errors
          Shane Smith

          Looks like it is trying to update a CI that it expects to find in the target CMDB dataset.  I would try finding the CI in the dataset by searching for that recon id found in the logs. To resolve it, you will probably need to complete a resync between Discovery and the CMDB dataset.

          • 2. Re: CMDB sync errors
            Duncan Grisby

            Something has changed the data in Discovery's dataset in the CMDB, so some CIs that Discovery thinks are there do not exist. Perhaps the CMDB was reverted to a backup?

             

            Discovery knows how to handle this situation, so you don't necessarily need to do anything. The next time it wants to sync those CIs, it will know that they were missing last time so it will create them. If you are drowning in a vast number of errors, you could do a resync, which will ensure that the CMDB dataset contains exactly what Discovery expects.

            3 of 3 people found this helpful