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

SF_Refresh failing intermittently: INVALID_REPLICATION_DATE

We have SF_Refresh scheduled to run every 30 mins for a few dozen tables. Then a full replicate runs weekly. Overnight (Saturday 10/28 into Sunday 10/29) the refresh started failing frequently (randomly on different tables) with an error something like the one below. I successfully ran SF_Replicate for all the tables thinking that would reset the incremental date being tracked, but it still continues to fail incrementally. Note that this occurred at 1:00 (DB Server time), but the error message indicates that DBAmp was using a start date of 2017-10-29 12:00:00 -- one hour earlier... not sure if that is expected or not.,

Ending SF_Refresh. Operation FAILED. [SQLSTATE 42000] (Error 50000) --- Starting SF_Refresh for Account V3.4.9 [SQLSTATE 01000] (Error 0) 13:00:01: Using Schema Error Action of subset [SQLSTATE 01000] (Error 0) 13:00:03: Using last run time of 2017-10-29 12:00:00 [SQLSTATE 01000] (Error 0) 13:00:04: Identified 0 updated/inserted rows. [SQLSTATE 01000] (Error 0) OLE DB provider "DBAmp.DBAmp" for linked server "SALESFORCE" returned message "Error 1 : INVALID_REPLICATION_DATE: startDate must be at least one minute greater than endDate". [SQLSTATE 01000] (Error 7412) 13:00:04: Error occurred fetching deleted rows. [SQLSTATE 01000] (Error 0) 13:00:04: Error: Cannot execute the query "Select Id from Account_Deleted where startdate='2017-10-29 12:00:00'" against OLE DB provider "DBAmp.DBAmp" for linked server "SALESFORCE". [SQLSTATE 01000] (Error 0) --- Ending SF_Refresh. Operation FAILED. [SQLSTATE 01000] (Error 0). The step failed.
1 person has
this problem
+1
Reply