Error: ORA-00001: unique constraint (PBDS.PK_T2B_DUPLICATE_MERGES) violated - during BBEC M2 sync

The M2 sync with BBEC may end right after starting with this error:
6/17/2015 6:00:19 AM START [TADATASYNC] Beginning of package execution.

6/17/2015 6:00:19 AM INFO [Acquire Lock] Lock has been acquired.
6/17/2015 6:00:19 AM PROGRESS [Lookup Sync Changeagent] Executing query "select ID from changeagent where username='Data Sy...".(100%)
6/17/2015 6:00:28 AM INFO [Check Control Key] Control key successfully located.
6/17/2015 6:00:28 AM PROGRESS [Clear NewErrors Flag] Executing query "update dbo.B2TCONTROL set NEWERRORS=0".(100%)
6/17/2015 6:02:13 AM PROGRESS [Initialize TA] Executing query "begin t2b_sync_initialize; end;".(100%)
6/17/2015 6:02:15 AM PROGRESS [Truncate t2b_bbec_deleted_names] Executing query "truncate table t2b_bbec_deleted_names".(100%)
6/17/2015 6:02:16 AM INFO [Log Deleted BBEC Constituents] "component "t2b_bbec_deleted_names" (50)" wrote 6 rows.

6/17/2015 6:02:26 AM ERROR [t2b_merge] Executing the query "begin t2b_merge.process_merges; end;" failed with the following error: "ORA-00001: unique constraint (PBDS.PK_T2B_DUPLICATE_MERGES) violated
ORA-06512: at "PBDS.T2B_MERGE", line 336
ORA-06512: at line 1". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
This may occur when the Sync tries to insert a second instance of a Dupe_Account_Id into a sync table. Contact support to investigate what record is causing the problem.



Was this article helpful?