Help get this topic noticed by sharing it on Twitter, Facebook, or email.
I’m frustrated

SF_ReplicateAll Fails on Custom Setting Object

Sql Agent to run SF_ReplicateAll nightly. Gets through first three tables and fails on fourth.

How does DBAmp handle Custom Settings (in this case, points to an AWS bucket)?

--- Starting SF_Replicate for AWS__c V3.6.2 [SQLSTATE 01000] (Message 0) 21:00:28: Parameters: SALESFORCE AWS__c Version: V3.6.2 [SQLSTATE 01000] (Message 0) 21:00:28: Drop AWS__c_Previous if it exists.... The step failed.

AWS__c is a custom setting pointing to an S3 bucket. SF_ReplicateAll ran fine
Ran query below and table still exists in Salesforce:

Select * from SALESFORCE...sys_sfobjects

I dropped the existing table of AWS__c but still the stored procedure fails on this object / table.

Should all custom setting be in the TablesToSkip table?

Thanks for any help anyone can offer.
1 person has
this problem
+1
Reply
  • Can you try running the following in a new query window and post the complete message output from it:

    exec SF_Replicate 'SALESFORCE', 'AWS__c'
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Ran successfully. Only one row.

    07:10:03: Parameters: SALESFORCE AWS__c Version: V3.6.2
    07:10:03: Drop AWS__c_Previous if it exists.
    07:10:03: Create AWS__c_Previous with new structure.
    07:10:04: DBAmpNet2 3.6.2.0 (c) Copyright 2015-2017 forceAmp.com LLC
    07:10:05: Parameters: replicate AWS__c_Previous AWOAP032 salesforce backups SALESFORCE
    07:10:07: 1 rows copied.
    07:10:07: DBAmpNet2 Operation successful.
    07:10:07: Drop AWS__c if it exists.
    07:10:07: Rename previous table from AWS__c_Previous to AWS__c
    Caution: Changing any part of an object name could break scripts and stored procedures.
    07:10:07: Create primary key on AWS__c
    --- Ending SF_Replicate. Operation successful.

    Ran Select * from SALESFORCE...sys_sfobjects

    refreshed list of table. it is there AWS__c

    Trying to run Agent with SF_ReplicateAll now
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • In order to diagnose why the SF_ReplicateAll failed we need to see the complete message output, but from the screenshot above it looks truncated.

    Can you go to the advanced tab of the job step and check the option to save the job output to a table. Then when the job fails, return to the Advanced tab and hit VIEW. This will display the complete message output.

    Please forward that to support at forceamp.com.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I’m thankful
    Thanks much to Justin and Bill for working through this with me.

    Two issues identified:

    1. I needed to update to ver 3.6.5 to fix bug on RecordActions Table schema update.
    2. Bill showed me to look for error: in logfile, not focus on last table updated. This led me to timeout on very large table that needs to be skipped and replicated separately.

    Update completed, table skipped and successful run of SP.

    Have a great 4th everyone!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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