Data Transmission Service:Common error codes that may be returned when you configure DTS tasks and corresponding solutions

DTS.Msg.LXCreateOrderError

• Cause: You cannot purchase a cross-border data synchronization instance because the unique ID (UID) of your account is not added to the whitelist.
• Solution: Obtain the cross-border data synchronization permissions and try again. For more information, see Apply for permissions to synchronize data across borders.

DTS.Msg.InvalidParameter.KafkaHostInvalid

• Cause: You cannot enter a domain name in the IP Address field.
• Solution: You can enter only an IP address in the IP Address field. Enter a valid private IP address and try again.

DTS.Msg.InvalidParameter.KafkaBrokerInvalid

• Cause: You cannot configure a Kafka node by using a domain name.
• Solution: Configure the Kafka node based on the following format:

  listeners=Protocol://Private IP address:Port number
  advertised_listeners=Protocol://Private IP address:Port number

DTS.Msg.OperationDenied.JobStatusModifying

• Cause: The instance to which the task belongs is in the Modifying Objects state.
• Solution: Wait until the state of the instance changes to Running and try again.

DTS.Msg.InvalidParameter.AliyunUidFormat

• Cause: The ID of the Alibaba Cloud account to which the source database instance belongs is invalid.
• Solution: Enter a valid Alibaba Cloud account ID.

DTS.Msg.DuplicateAccount.RDSSqlServer

• Cause: The instance is already involved in another DTS task or the instance is a cloned instance.
• Solution: Contact technical support.

DTS.Msg.SrcLink.InternetAddressNotFound

• Cause: The source database instance does not have a public endpoint.
• Solution: Apply for a public endpoint for the source database instance or configure a data synchronization task.

DTS.Msg.UpdateJob.OperationDenied.InitStatus

• Cause: You cannot configure a data synchronization task that is already started.
• Solution: Reset the task or reselect the objects to be synchronized.
  Warning After you reset a task, the original configurations of the task are overwritten.

DTS.Msg.Throttling.User

• Cause: The number of API requests has reached the threshold.
• Solution: Initiate a request 15 to 30 seconds later.

DTS.Msg.LXCreateOrder.NotFoundPricePlan

• Cause: You specify an invalid parameter when you call an API operation to create a DTS instance, or you cannot purchase a DTS instance of the specified type.
• Solution: Check whether the specified parameters are valid. If the parameters are valid, contact technical support.

DTS.Msg.LXPayOrder.InsufficientBalance

• Cause: Your account balance is insufficient.
• Solution: Add funds to your account and try again.

DTS.Msg.CheckStatus.InvalidInitStatus

• Cause: The data synchronization task is not configured.
• Solution: Complete the configurations of the task before you modify the task.

DTS.Msg.DRDSInvokeFail.DatabaseAuthorizationFailed

can not getTableTopology (drds****,ib_ibos****)
Could not connect to address=(host=100.100.XX.XX)(port=****)(type=master) : (conn=****) [10.0.1.1:3306]
Access denied for user 'ib_ibos****'@'100.104.XX.XX' to database 'ib_ibos****')

• Cause: The specified database account does not have the required permissions on the database.
• Solution: Manually modify the permissions on the database that are granted to the database account by performing the following steps:
  1. Log on to the PolarDB-X console.
  2. In the left-side navigation pane, click Instance List. On the Instance List page, click the name of the instance that you created.
  3. In the left-side navigation pane, choose Configuration and Management > Accounts.
  4. Find the created database account and click Modify Permissions in the Actions column. In the dialog box that appears, add or modify the permissions on the database.
  5. Click OK.

DTS.Msg.DescribeColumns.TimeOut

• Cause: The source database has a large number of columns or is read at an excessively slow speed. As a result, the process of obtaining the source database schema times out.
• Solutions:
  • Call the relevant API operation to obtain the schema of the source database.
  • Check the speed at which the source database is read.

DTS.Msg.DescribeStruct.TimeOut

• Cause: The source database has a large number of columns or is read at an excessively slow speed. As a result, the process of obtaining the source database schema times out.
• Solution:
  • Specify the source database as the object to be synchronized or migrated. This way, DTS does not obtain detailed information about tables in the source database.
  • Call the relevant API operation to obtain the schema of the source database.
  • Check the speed at which the source database is read.

DTS.Msg.DRDSErrExecuteOnMySQL.ClientVersionTooLow

• Cause: The version of the PolarDB-X database is earlier than required.
• Solution: Update the PolarDB-X database to a version that meets the requirements.

DTS.Msg.DbTypeNotSupport.OnlyReadRDS

• Cause: The source database instance is a read-only PolarDB-X instance.
• Solution: Change the source database instance to a primary PolarDB-X instance.

DTS.Msg.DbTypeNotSupport.PolarDBRDS

• Cause: The source database instance is a PolarDB-X instance whose storage type is PolarDB.
• Solution: Change the source database to a PolarDB-X instance whose storage type is ApsaraDB RDS for MySQL.

DTS.Msg.OperationDenied.NotPurchased

• Cause: The DTS task that you start is not purchased.
• Solution: Purchase the DTS task and then start the DTS task.

DTS.Msg.CheckJobFailed.ServerUnAvailable

• Cause: The system cannot connect to the server on which the DTS task runs. As a result, you cannot perform a connectivity test on the source or destination database.
• Solution: Contact technical support.

DTS.Msg.StopJobFailed.ServerUnAvailable

• Cause: The system cannot connect to the server on which the DTS task runs. As a result, the DTS task cannot be paused as required.
• Solution: Contact technical support.

DTS.Msg.SQLExecuteError.JDBC4CommunicationsException

• Cause: An error occurs during data communication. The packet of the Java Database Connectivity (JDBC) driver is sent to the source database server, but no packet is received from the source database server.
• Solution:
  • Check whether the database has a large number of connections.
  • Refer to the solutions in Solving a "communications link failure" with JDBC and MySQL.
  • Contact technical support.

DTS.Msg.SQLExecuteError.ConnectionRefused

• Cause: Your request to connect to the source database is denied.
• Solution:
  • Check whether the listener process runs as expected. If not, check whether the listener process is properly configured.
  • Check whether the load is high.
  • Contact technical support.

DTS.Msg.GetKafkaMetaInfo.NoAvailableBroker

• Cause:
  • You enter an incorrect username or password of the database.
  • You cannot obtain MetaInfo from the Kafka broker.
• Solution:
  • Enter the correct username and password. If authentication is disabled for the Kafka cluster, you do not need to enter the username and password.
  • Check whether the bootstrap.servers parameter of the Kafka broker is properly set.
  • Check whether the version of the Kafka cluster in which the destination database resides meets the requirement.
  • Check whether the network connection is established.

DTS.Msg.GetMongoDbShardInfo.EmptyInstances

• Cause: You cannot obtain the information about shards.
• Solution: Check the configurations of the MongoDB database to ensure that the database is sharded.

DTS.Msg.GetMongoDbShardInfo.NoShardAddress

• Cause: You cannot obtain the information about shards.
• Solution: Check the configurations of the MongoDB database to ensure that the database is sharded. Apply for endpoints for the shards. For more information about how to apply for endpoints for the shards, see Apply for an endpoint for a shard or Configserver node.

DTS.Msg.SuspendDenied.JobStatusModifying

• Cause: A DTS task in the Modifying Objects state cannot be stopped. This prevents data inconsistency.
• Solution:
  • One task: Wait until the Modifying Objects state ends.
  • Multiple tasks: Remove tasks in the Modifying Objects state or wait until the state ends.

DTS.Msg.ModifyDenied.JobStatusNotRunning

• Cause: The objects to be synchronized in a DTS task that is stopped cannot be modified. This prevents data inconsistency.
• Solution: Start the task, wait until the state of the task changes to Running, and then try again.
  Note If the latency of the task exceeds 10 minutes, do not modify the objects to be synchronized.

DTS.Msg.LXPayOrder.AmountLimitExceeded

• Cause: The order amount for an account that has the Proof of Concept (POC) tag can only be 0. Payment cannot be made for an order whose amount is greater than 0.
• Solution:
  • Use a voucher to pay for your order so that the payment amount changes to 0.
  • Use another account to purchase the DTS task.
  Note You must cancel failed orders in the User Center instead of trying to pay for them again.

DTS.Msg.LXPayOrder.AccountBookNotExists

• Cause: You did not add funds to your Alibaba Cloud account or your account balance is insufficient.
• Solution: Add funds to your account, make sure that your account balance is sufficient, and then try again.
  Note You must cancel failed orders in the User Center instead of trying to pay for them again.

DTS.Msg.ConfigJob.NoneSelectedStep

• Cause: The StructureInitialization, DataInitialization, and DataSynchronization parameters are all set to false.
• Solution: Set these parameters to valid values to configure the task steps.

DTS.Msg.ConfigJob.InvalidDbListFormat

• Cause: The value of the DbList parameter is set to an invalid JSON string.
• Solution: Set the value of the parameter to a valid JSON string.

DTS.Msg.ConfigJob.InvalidReserveFormat

• Cause: The value of the Reserve parameter is set to an invalid JSON string.
• Solution: Set the value of the parameter to a valid JSON string.

DTS.Msg.DistributedDatabaseNodesError

• Cause: The number of nodes of the distributed database is inconsistent with the value of the Nodes of a Distributed Database parameter that is set when you purchase the DTS instance.
• Solution: You must set the value of the Nodes of a Distributed Database parameter to a value that is the same as the number of nodes of the distributed database.

DTS.Msg.LXQueryOrder.NotFoundNormalOrder

• Cause:
  • The instance is complete but is not released.
  • The instance has been released but is still displayed in the console.
• Solution:
  • Release the instance that is complete.
  • If the instance has been released but is still displayed in the console, contact technical support.

DTS.Msg.GetSSLInfo.NoSSLConn

• Cause: SSL encryption is disabled for the instance that you configure.
• Solution: Enable SSL encryption for the instance or set the Encryption parameter to Non-encrypted.

DTS.Msg.ModifyDynamicConfig.InvalidStatus

• Cause: The task is not in the Running state.
• Solution: Make sure that the task is in the Running state and try again.

DTS.Msg.TransferInstanceClass.NoPermission

• Cause: The RAM user that performs the operation does not have the permissions to downgrade the configurations of a DTS instance.
• Solution: Contact technical support to obtain the permissions to downgrade the configurations of a DTS instance for the RAM user and the Alibaba Cloud account to which the RAM user belongs.

DTS.Msg.OperationDenied.ConsumerGroupOutOfUsage

• Cause: The change tracking instance already has more than 20 consumer groups.
• Solution: Delete the consumer groups that you no longer use based on your business requirements and try again.

DTS.Msg.GrantAccessAlreadyExists

• Cause: An occasional error occurred.
• Solution: Try again. If the error persists, contact technical support.

DTS.Msg.DbListIsEmpty

• Cause: The value of the DbList parameter is set to null, or the value of the parameter that you set is equivalent to null.
• Solution: Set the value of the DbList parameter to a value that is not null. For more information, see Objects of DTS tasks.

DTS.Msg.GetRedisNodes.NotCluster

• Cause: The Instance Mode parameter is not set based on the architecture of the Redis database.
• Solution: Set the Instance Mode parameter based on the architecture of the Redis database.

DTS.Msg.InvalidDestinationEndPointRegion

• Cause: You enter an invalid value in the Instance Region field for the destination instance, or you specify a region that is not supported by DTS.
• Solution: Specify a valid region for the destination instance. For more information, see List of supported regions.

DTS.Msg.InvalidSourceEndPointRegion

• Cause: You enter an invalid value in the Instance Region field for the source instance, or you specify a region that is not supported by DTS.
• Solution: Enter a valid region for the source instance. For more information, see List of supported regions.

DTS.Msg.AdminAccountExists

• Cause: DTS creates a privileged account for some types of source databases. If the account created by DTS already exists in the source database, this error is reported.
• Solution: Contact technical support.

DTS.Msg.NotSupportModify

• Cause: The value of the DtsInstanceId parameter is set to the ID of a migration instance.
• Solution: You can modify only the ETL configurations of a migration task in the console. If you need to modify other configurations of a migration task, you can create another task.

DTS.Msg.PrePayNotAllowDelete

• Cause: A DTS task that uses the subscription billing method cannot be released.
• Solution: Do not release a DTS task that uses the subscription billing method.

DTS.Msg.Forbidden.AliyunUIDNotFound

• Cause: The information of the Alibaba Cloud account used to log on to the DTS console is not initialized.
  • For a DTS task in which data is replicated across Alibaba Cloud accounts, the Alibaba Cloud account to which the source database belongs has never been used to log on to the DTS console.
  • If you log on to the DTS console as a RAM user, the Alibaba Cloud account to which the RAM user belongs has never been used to log on to the DTS console.
• Solution: View the UID in the error message, log on to the DTS console by using the corresponding Alibaba Cloud account, and then try again.

DTS.Msg.RamPermissionDenied

• Cause: The RAM user does not have the permissions that are required to perform the operations.
• Solution: Grant the permissions to the RAM user and try again. For more information, see Use a system policy to authorize a RAM user to manage DTS instances or Use a custom policy to authorize a RAM user to manage DTS instances.
  Note When you create a custom policy, you need to use the Action and ResourcedId information displayed in the error message.
  

DTS.Msg.EcsJoinSecurityGroupLimitExceeded

• Cause: The ECS instance has been added to five security groups.
• Solution: Remove the ECS instance from unnecessary security groups based on your business requirements and try again. For more information, see Remove an instance from a security group.
  Note If the ECS instance cannot be removed from some security groups due to business requirements, adjust the security groups of the ECS instance to make sure that the number of security groups does not exceed five.