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

Exceeded_ID_Limit on SF_Refresh

We are receiving this error for all of our history objects when we attempt to execute a SF_RefreshAll. I believe the cause may have to do with the fact that I think the getDeleted() API call will supposedly return all deleted records from all history objects, not just the object that is referenced in the call. I am assuming that our delete log for all of the history objects may have exceeded this 600,000 record limit. How can I work around this limitation to still refresh these objects?

[SQLSTATE 01000] (Message 0) OLE DB provider "DBAmp.DBAmp" for linked server "SFDC" returned message "Error 1 : EXCEEDED_ID_LIMIT: there are '600000' or more records deleted in the specified time period. Please retry getDeleted() call using a shorter time period". [SQLSTATE 01000] (Message 7412) 02:01:35: Error occurred fetching deleted rows. [SQLSTATE 01000] (Message 0) 02:01:35: Error: Cannot execute the query "Select Id from AccountHistory_Deleted where startdate='2014-03-11 01:31:00'" against OLE DB provider "DBAmp.DBAmp" for linked server "SFDC". [SQLSTATE 01000] (Message 0) --- Ending BB_SF_Refresh. Operation FAILED. [SQLSTATE 01000] (Message 0) Error: BB_SF_Refresh failed for table AccountHistory [SQLSTATE 01000] (Message 0) Error 50000, Severity 16, State 1, Line 926 [SQLSTATE 01000] (Message 0) --- Ending SF_Refresh. Operation FAILED. [SQLSTATE 01000] (Message 0) --- Starting BB_SF_Refresh for AccountPartner [SQLSTATE 01000] (Message 0) 02:01:36: Using Schema Error Action of yes [SQLSTATE 01000] (Message 0) 02:01:36: Using last run time of 2014-03-11 01:32:00 [SQLSTATE 01000] (Message 0) 02:01:36: Identified 0 updated/inserted rows. [SQLSTATE 01000] (Message 0) 02:01:36: Using alternate method to determine deleted records.
1 person has
this problem
+1
Reply
  • You will need to run a sf_replicat on that object because you have too many deletes to run sf_refresh. Wait 1hour after the replicate finishes and then you resume your normal sf-refresh schedule.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Hi Bill, thanks for the reply.

    I tried your suggestion on my AccountHistory object, but even after an hour has passed if I attempt to run a refresh on the history table that was replicated I still get the error. I found this note below on the salesforce API documentation site, which I believe may be involved with how dbAmp is attempting to determine which records to delete from my local copy of any history object. This error suddenly started to occur for us today. We have a daily scheduled refresh-all which has been working away for months now without the problem. Is there any work around where I won't need to wait until the delete log is purged to get us back under a total of 600,000 records deleted in all history objects within the delete log? Is the 600,000 record limit a salesforce limit of the API? Or if I am not correct with my assumptions here, please let me know as well.

    This is the note I found regarding getDeleted which I think dbAmp is attempting to use to determine the deleted records:

    "If you call getDeleted() for a history object, the call returns the records deleted during the given date range for all history objects, not only the history object you specified. For example, if you call getDeleted() for AccountHistory, you’ll get records deleted during the given date range for AccountHistory, ContactHistory, and so on."
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Can you post the complete output of the sf_refresh ?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • This reply was removed on 2014-03-12.
    see the change log
  • I may have spoken too soon with my last reply. I was just now able to run SF_Refresh on AccountHistory without error this time. I will post the output if I continue to have a problem.

    Thank you for your help.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Hi Bill, we had a successful run of our SF_RefreshAll again last night, so I believe you can consider this case closed. I will return and post any error details here should it come up again.

    Thanks!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated