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

Salesforce table does not exist [DBAmp 3.1.4]

We run many Refresh commands in a SQL job every 30 minutes. For the last two days the 5:00aEST execution has failed with a "Salesforce table does not exist" message. These tables are never deleted and the Refresh resumes/continues to work for a subsequent executions.

I know our version is getting old, but from other problem tickets it seems like our version is after a couple of bug fixes. Any assistance would be appreciated.
1 person has
this question
+1
Reply
  • Can you post the complete message output from the failed command? Also what version are you running?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Running DBAmp version 3.1.4.

    Complete message below. Failure at the end. Worked at 05:30.

    Job 'SF_Refresh_30minutes' : Step 1, 'sp__SF_Refresh_sf_tables' : Began Executing 2018-11-09 05:00:00

    ~~Start: getdate()="Nov 9 2018 5:00AM" @time="05:00" [SQLSTATE 01000]
    --- Starting SF_Refresh for AccountContactRole V3.1.4 [SQLSTATE 01000]
    05:00:01: Using last run time of 2018-11-09 04:00:00 [SQLSTATE 01000]
    05:00:02: Identified 0 updated/inserted rows. [SQLSTATE 01000]
    05:00:02: Identified 0 deleted rows. [SQLSTATE 01000]
    --- Ending SF_Refresh. Operation successful. [SQLSTATE 01000]
    --- Starting SF_Refresh for AccountTeamMember V3.1.4 [SQLSTATE 01000]
    05:00:02: Using last run time of 2018-11-09 04:00:00 [SQLSTATE 01000]
    05:00:02: Identified 0 updated/inserted rows. [SQLSTATE 01000]
    05:00:03: Identified 0 deleted rows. [SQLSTATE 01000]
    --- Ending SF_Refresh. Operation successful. [SQLSTATE 01000]
    --- Starting SF_Refresh for Account_Country__c V3.1.4 [SQLSTATE 01000]
    05:00:03: Using last run time of 2018-11-09 04:00:00 [SQLSTATE 01000]
    05:00:03: Identified 0 updated/inserted rows. [SQLSTATE 01000]
    05:00:03: Identified 0 deleted rows. [SQLSTATE 01000]
    --- Ending SF_Refresh. Operation successful. [SQLSTATE 01000]
    --- Starting SF_Refresh for Campaign V3.1.4 [SQLSTATE 01000]
    05:00:04: Using last run time of 2018-11-09 04:00:00 [SQLSTATE 01000]
    05:00:04: Identified 0 updated/inserted rows. [SQLSTATE 01000]
    05:00:04: Identified 0 deleted rows. [SQLSTATE 01000]
    --- Ending SF_Refresh. Operation successful. [SQLSTATE 01000]
    --- Starting SF_Refresh for CampaignMember V3.1.4 [SQLSTATE 01000]
    05:00:04: Using last run time of 2018-11-09 04:00:00 [SQLSTATE 01000]
    05:00:05: Identified 0 updated/inserted rows. [SQLSTATE 01000]
    05:00:05: Identified 0 deleted rows. [SQLSTATE 01000]
    --- Ending SF_Refresh. Operation successful. [SQLSTATE 01000]
    --- Starting SF_Refresh for CAS_Master__c V3.1.4 [SQLSTATE 01000]
    05:00:05: Using last run time of 2018-11-09 04:00:00 [SQLSTATE 01000]
    05:00:05: Identified 0 updated/inserted rows. [SQLSTATE 01000]
    05:00:05: Identified 0 deleted rows. [SQLSTATE 01000]
    --- Ending SF_Refresh. Operation successful. [SQLSTATE 01000]
    --- Starting SF_Refresh for Product_SDS_Template__c V3.1.4 [SQLSTATE 01000]
    05:00:06: Using last run time of 2018-11-09 04:00:00 [SQLSTATE 01000]
    05:00:06: Identified 0 updated/inserted rows. [SQLSTATE 01000]
    05:00:06: Identified 0 deleted rows. [SQLSTATE 01000]
    --- Ending SF_Refresh. Operation successful. [SQLSTATE 01000]
    --- Starting SF_Refresh for CategoryData V3.1.4 [SQLSTATE 01000]
    05:00:06: Using last run time of 2018-11-09 04:00:00 [SQLSTATE 01000]
    05:00:06: Identified 0 updated/inserted rows. [SQLSTATE 01000]
    05:00:07: Identified 0 deleted rows. [SQLSTATE 01000]
    --- Ending SF_Refresh. Operation successful. [SQLSTATE 01000]
    --- Starting SF_Refresh for CategoryNode V3.1.4 [SQLSTATE 01000]
    05:00:07: Using last run time of 2018-11-09 04:00:00 [SQLSTATE 01000]
    05:00:07: Identified 0 updated/inserted rows. [SQLSTATE 01000]
    05:00:07: Identified 0 deleted rows. [SQLSTATE 01000]
    --- Ending SF_Refresh. Operation successful. [SQLSTATE 01000]
    --- Starting SF_Refresh for Contact V3.1.4 [SQLSTATE 01000]
    05:00:08: Using last run time of 2018-11-09 04:00:00 [SQLSTATE 01000]
    05:00:08: Identified 0 updated/inserted rows. [SQLSTATE 01000]
    05:00:08: Identified 0 deleted rows. [SQLSTATE 01000]
    --- Ending SF_Refresh. Operation successful. [SQLSTATE 01000]
    --- Starting SF_Refresh for Department__c V3.1.4 [SQLSTATE 01000]
    05:00:08: Using last run time of 2018-11-09 04:00:00 [SQLSTATE 01000]
    05:00:08: Identified 0 updated/inserted rows. [SQLSTATE 01000]
    05:00:09: Identified 0 deleted rows. [SQLSTATE 01000]
    --- Ending SF_Refresh. Operation successful. [SQLSTATE 01000]
    --- Starting SF_Refresh for Employee__c V3.1.4 [SQLSTATE 01000]
    05:00:09: Using last run time of 2018-11-09 04:00:00 [SQLSTATE 01000]
    05:00:09: Identified 0 updated/inserted rows. [SQLSTATE 01000]
    05:00:09: Identified 0 deleted rows. [SQLSTATE 01000]
    --- Ending SF_Refresh. Operation successful. [SQLSTATE 01000]
    --- Starting SF_Refresh for Forecast__History V3.1.4 [SQLSTATE 01000]
    05:00:09: Using last run time of 2018-11-09 04:00:00 [SQLSTATE 01000]
    05:00:10: Identified 0 updated/inserted rows. [SQLSTATE 01000]
    05:00:10: Identified 0 deleted rows. [SQLSTATE 01000]
    --- Ending SF_Refresh. Operation successful. [SQLSTATE 01000]
    --- Starting SF_Refresh for Forecast_Product__c V3.1.4 [SQLSTATE 01000]
    05:00:10: Using last run time of 2018-11-09 04:00:00 [SQLSTATE 01000]
    05:00:10: Identified 0 updated/inserted rows. [SQLSTATE 01000]
    05:00:10: Identified 0 deleted rows. [SQLSTATE 01000]
    --- Ending SF_Refresh. Operation successful. [SQLSTATE 01000]
    --- Starting SF_Refresh for Lead V3.1.4 [SQLSTATE 01000]
    05:00:11: Using last run time of 2018-11-09 04:00:00 [SQLSTATE 01000]
    05:00:11: Identified 1 updated/inserted rows. [SQLSTATE 01000]
    05:00:11: Identified 0 deleted rows. [SQLSTATE 01000]
    05:00:11: Adding updated/inserted rows into Lead [SQLSTATE 01000]
    --- Ending SF_Refresh. Operation successful. [SQLSTATE 01000]
    --- Starting SF_Refresh for New_Business__c V3.1.4 [SQLSTATE 01000]
    05:00:12: Using last run time of 2018-11-09 04:00:00 [SQLSTATE 01000]
    05:00:12: Identified 0 updated/inserted rows. [SQLSTATE 01000]
    05:00:12: Identified 0 deleted rows. [SQLSTATE 01000]
    --- Ending SF_Refresh. Operation successful. [SQLSTATE 01000]
    --- Starting SF_Refresh for Nonconformance_Form__c V3.1.4 [SQLSTATE 01000]
    05:00:12: Using last run time of 2018-11-09 04:00:00 [SQLSTATE 01000]
    05:00:13: Identified 0 updated/inserted rows. [SQLSTATE 01000]
    05:00:13: Identified 0 deleted rows. [SQLSTATE 01000]
    --- Ending SF_Refresh. Operation successful. [SQLSTATE 01000]
    --- Starting SF_Refresh for Note V3.1.4 [SQLSTATE 01000]
    05:00:13: Using last run time of 2018-11-09 04:00:00 [SQLSTATE 01000]
    05:00:13: Identified 0 updated/inserted rows. [SQLSTATE 01000]
    05:00:13: Identified 0 deleted rows. [SQLSTATE 01000]
    --- Ending SF_Refresh. Operation successful. [SQLSTATE 01000]
    Msg 50000, Sev 16, State 1, Line 796 : --- Ending SF_Refresh. Operation FAILED. [SQLSTATE 42000]
    Msg 0, Sev 16, State 1, Line 47 : --- Starting SF_Refresh for Opp_Forecast__c V3.1.4 [SQLSTATE 01000]
    Msg 0, Sev 16, State 1, Line 159 : 05:00:13: Error: Salesforce table does not exist: Opp_Forecast__c [SQLSTATE 01000]
    Msg 0, Sev 16, State 1, Line 793 : --- Ending SF_Refresh. Operation FAILED. [SQLSTATE 01000]
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • The issue with that older version that the underlying error message is not surfaced in the output. If it happens at the same time, then I would suspect that you have reached the hard limit of 10 simultaneously open queries on Salesforce.

    Have you recently added additional new DBAmp that now runs at the time of the error.?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Have you recently added additional new DBAmp that now runs at the time of the error.?....
    No, we single thread our jobs.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • FYI... Worked normally through 11/07. Failed at 5:00aEST on 11/08 and 11/09. Worked normally on 11/10, 11/11, 11/12.

    Our server is normally in Belcamp, MD. We are in the middle of a Disaster Recovery test at this time. We are running on our DR servers in Memphis, TN. Will fall back to the normal servers by midnight tonight. So that the 11/13 execution will be back on the normal server.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • So maybe there is a loss of network connectivity right at that time ?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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