Share product questions and get support for CData DBAmp
- 11 Topics
- 13 Replies
DBAMP Patches and Hotfix Plans
Is there a patch / hotfix official release schedule for DBAMP? There must be some fixes since the official V2022 release. I did get some Hotfix patches but was wondering if I am to expect an official 2023 or 2022.1 release. I currently have to restart the windows service each night to prevent crashes.
I can't run any command using bulkapi!
Whenever I try to use the bulkapi, or pkchunk, or even just use SF_Mirror on a large table, it says that SF_Mirror fails. The message output looks like this:--- Starting SF_Mirror for Account V830410:53:19: Parameters: salesforce2022 Account bulkapi Version: V830410:53:19: DBAmpAZ 22.0.8304.0 Copyright c 2021 CData Software, Inc.10:53:19: Using options specified in Options parameter: bulkapi10:53:19: Obtaining Connection Props10:53:28: Obtaining User Information10:53:31: Using settings from Registry.10:53:33: Error: DBAmpWork directory does not exist.10:53:33: DBAmpAZ Operation FAILED.10:53:33: Error: MirrorCopy program was unsuccessful.10:53:33: Error: Command string is C:\"Program Files"\CData\"CData DBAmp"\bin\DBAmpAZ.exe MirrorCopy "Account" "DL-7KVJRL3" "salesforce_backups2022" "salesforce2022" "bulkapi"--- Ending SF_Mirror. Operation FAILED.Msg 50000, Level 16, State 1, Procedure sf_mirror, Line 173 [Batch Start Line 1]--- Ending SF_Mirror. Operation FAILED.
Replicating fails for my big tables
When I run SF_Replicate on my tables with lots of fields, like Account and Case, it fails. SF_Mirror also fails, and I can’t run SF_Refresh because there’s been a field added so it just tries to run SF_Replicate anyway. The message output looks like this:--- Starting SF_Replicate for Account V5.1.812:58:41: Parameters: Salesforce Account Version: V5.1.812:58:41: DBAmpAZ 184.108.40.206 Copyright c 2021 CData Software, Inc.12:58:41: Using options specified in Options parameter: soap12:58:42: Using settings from Registry.12:58:42: Using FullCopy to replicate the Account table.12:58:42: Server: DL-7KVJRL3, Database: olddbamp, Linked Server: Salesforce12:58:42: Using the Salesforce SOAP API.12:58:43: Opening SQL Server rowset12:58:43: Error: Commit failed.Source: Microsoft SQL Server Native Client 11.0Description: The statement has been terminated.Source: Microsoft SQL Server Native Client 11.0Description: Cannot create a row of size 8107 which is greater than the allowable maximum row size of 80
New standard fields not showing up
Salesforce added a couple new fields to the Contact and Lead objects, GenderIdentity and Pronouns. I can find them in Data Loader and in Workbench, but DBAmp is not bringing them down. How do I get DBAmp to find those new fields? I have DBAmp v22, if that makes a difference.
I upgraded and now my stored procedures don't work
I upgraded to v22, and followed the instructions to set up a new linked server. Querying it works fine, but I can’t use the stored procedures. I get something like this every time:--- Starting SF_Replicate for account V5.1.811:34:36: Parameters: salesforce2022 account Version: V5.1.811:34:36: DBAmpAZ 220.127.116.11 Copyright c 2021 CData Software, Inc.11:34:36: Using options specified in Options parameter: soap11:34:40: Retrying11:34:40: Retrying11:34:40: Retrying11:34:40: Error: Unable to retrieve settings from Registry.11:34:40: System.Data.SqlClient.SqlException (0x80131904): The OLE DB provider "MSOLEDBSQL" for linked server "salesforce2022" does not contain the table "sys_sfsession". The table either does not exist or the current user does not have permissions on that table. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateO
Do I have to name the database salesforce backups?
When I went through the directions here, https://cdn.cdata.com/help/AFH/dbampd/Installation_Upgrading.html it says to create a database for the stored procedures called salesforce backups. That doesn’t fit our naming conventions - is there a way around that?
DBAmp commands failing with timeout errors
Whenever I try to do anything with the linked server, I either get an error about the OLE DB provider returning a message that the “Login timeout expired” or “TCP Provider: The wait operation timed out.” Sometimes it also says "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible.” I can’t do anything with DBAmp, how do I fix this?
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.