Help get this topic noticed by sharing it on Twitter, Facebook, or email.

SF_ReplicateAll fails on same table each time since update of dbamp

We updated recently from 2.16 to 2.18.3 and now when we run the replicateall procedure it fails at the same point every time (sandbox or production)

Logfile will error

--- Ending SF_Replicate. Operation successful.
--- Starting SF_Replicate for uf__User_Status__c
10:30:05: Drop uf__User_Status__c_Previous if it exists.
10:30:05: Create uf__User_Status__c_Previous with new structure.
10:30:06: Run the DBAmp.exe program.
10:30:06: DBAmp Bulk Operations. V2.18.3 (c) Copyright 2006-2014 forceAmp.com LLC
10:30:06: Populating local table uf__User_Status__c_Previous , SRVDBS02 / SF_Vita_Test .
10:30:07: DBAmp is using the SQL Native Client.
10:30:07: Opening SQL Server rowset
10:30:09: 110 rows copied.
10:30:09: Drop uf__User_Status__c if it exists.
10:30:09: Rename previous table from uf__User_Status__c_Previous to uf__User_Status__c
Caution: Changing any part of an object name could break scripts and stored procedures.
10:30:09: Create primary key on uf__User_Status__c
--- Ending SF_Replicate. Operation successful.
--- Ending SF_ReplicateAll. Operation failed.
Msg 50000, Level 16, State 1, Procedure SF_ReplicateAll, Line 119
--- Ending SF_ReplicateAll. Operation FAILED.

The next table to replicate is uf__User_Status__History. Line 119 is Drop table #tmpsf or

ERR_HANDLER:
-- If we encounter an error, then indicate by returning 1
Drop table #tmpSF

If I use SF_Replicate on the same table I get no issue. If I use it on the one prior
(uf__User_Status__c) I get no issue.

I have read the forums help and tried looking for duplicate IDs but can't see any.

Any ideas to why it fails at this location every time the back up is run (weekly and manually)

Thanks in advance

Mike
1 person has
this problem
+1
Reply