3 Replies Latest reply on Sep 5, 2014 2:54 AM by Edwin van den Berg

    CMDB Sync error 105035

    Edwin van den Berg

      I'm currently getting this error when I try to sync a Host from ADDM to Atrium CMDB:

      1. ERROR (105035): ; The entry that you are trying to save already exists on the database. Please verify the categorization and try again.

      We flushed the ADDM Dataset in the CMDB, but still we are getting this error...

      We also deactivated all custom mapping extensions and are only using TKU mapping files now.

       

      Does anybody have an idea where this error comes from?

       

      ADDM 10.0.0.2, CMDB 8.0

        • 1. Re: CMDB Sync error 105035
          Lisa Keeler

          I've never seen this error.

           

          I would turn debug on for CMDB Sync logs, maybe run with just 1 thread (so the logs are easier to read), re-run the Sync, and open a ticket with Support.

           

          Or, send the complete error from the tw_cmdbsync_exporter.log file here.

          • 2. Re: CMDB Sync error 105035
            Edwin van den Berg

            Meanwhile I found out that the error occurs for most hosts, but not all.

            I also deselected everything except BMC_ComputerSystem and then, one by one, switched them on again.

            The problems started with various kinds. Not one specific kind.

             

            This is the complete error in in the tw_cmdbsync_exporter.log:

             

            Sync of xxxxxxxxxxxxxxxxxxxx: An error occurred during the sync transaction.

            com.tideway.integrations.cmdbsync.exception.CMDBAccessException: ERROR (105035): ; The entry that you are trying to save already exists on the database. Please verify the categorization and try again.

            at com.tideway.integrations.cmdbsync.provider.atrium76.Atrium76Connector.handleException(Atrium76Connector.java:336)

            at com.tideway.integrations.cmdbsync.provider.atrium76.Atrium76Connector.handleException(Atrium76Connector.java:289)

            at com.tideway.integrations.cmdbsync.provider.atrium76.Atrium76Connector.commit(Atrium76Connector.java:213)

            at com.tideway.integrations.cmdbsync.provider.atrium.AtriumGraphSync.processNonSharedNodeActions(AtriumGraphSync.java:248)

            at com.tideway.integrations.cmdbsync.provider.atrium.AtriumGraphSync.sync(AtriumGraphSync.java:107)

            at com.tideway.integrations.cmdbsync.provider.general.SyncProvider.sync(SyncProvider.java:148)

            at com.tideway.integrations.cmdbsync.CMDBSyncProvider.sync(CMDBSyncProvider.java:361)

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

            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)

            Caused by: ERROR (105035): ; The entry that you are trying to save already exists on the database. Please verify the categorization and try again.

            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.CMDBCreateMultipleInstances(Unknown Source)

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

            at com.tideway.integrations.cmdbsync.provider.atrium76.Atrium76Connector.commit(Atrium76Connector.java:209)

            ... 8 more

            • 3. Re: CMDB Sync error 105035
              Edwin van den Berg

              It seems that the normalization engine tried to match the CI with the product catalogue.

              Matching was set to CTI only (no manufacturer of model) and that the NE couldn't match and created the error and the sync failed. For now we have disabled inline-normalization and we can sync to the ADDM dataset now.

              We still have to work on the correct normalization settings.