Data Transmission Service:Common errors and troubleshooting

Overview

Common errors that may be returned when you configure a DTS task

DTS.Msg.LXCreateOrderError

Scenario: When you purchase a DTS instance, the order fails to be created.

Possible cause: You purchase a cross-border data synchronization instance but the ID of your Alibaba Cloud account is not added to the whitelist.

Solution: Apply for the permissions to synchronize data across borders and try again. For more information, see Apply for permissions to synchronize data across borders.

DTS.Msg.InvalidParameter.KafkaHostInvalid

Scenario: You configure a DTS task to replicate data to a Kafka cluster that is connected over Express Connect, VPN Gateway, or Smart Access Gateway.

Possible cause: You 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

Scenario: You configure a DTS task to replicate data to a self-managed Kafka cluster that is hosted on an Elastic Compute Service (ECS) instance.

Possible cause: You configure listeners on a Kafka node by using a domain name.

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

DTS.Msg.OperationDenied.JobStatusModifying

Scenario: You call the ModifyDtsJob operation to modify the configurations of a data synchronization task.

Possible cause: The DTS 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

Scenario: When you configure a data synchronization task to replicate data across Alibaba Cloud accounts, you select a database instance from the drop-down list.

Possible 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

Scenario: You specify an SQL Server database as the source or destination database of a DTS task.

Possible cause: The database instance is already used in another DTS task, or the instance is a cloned instance.

Solution: Contact Alibaba Cloud technical support.

DTS.Msg.SrcLink.InternetAddressNotFound

Scenario: You configure a cross-region data migration task.

Possible cause: The source database instance does not have a public endpoint.

Solution: Configure a public endpoint for the source database instance, or configure a data synchronization task.

DTS.Msg.UpdateJob.OperationDenied.InitStatus

Scenario: You configure a data synchronization task that is configured.

Possible cause: The data synchronization task is already started.

DTS.Msg.Throttling.User

Scenario: You use a DTS feature.

Possible cause: The maximum number of API requests is reached.

Solution: Initiate a request 15 to 30 seconds later.

DTS.Msg.LXCreateOrder.NotFoundPricePlan

Scenario: When you purchase a DTS instance, the order fails to be created.

Possible cause: You specify an invalid parameter when you call an API operation to create a DTS instance, or you purchase a DTS instance of a type that is not supported.

Solution: Check whether the specified parameters are valid and try again.

DTS.Msg.LXPayOrder.InsufficientBalance

Scenario: When you purchase a DTS instance, your payment fails.

Possible cause: Your account balance is insufficient.

Solution: Add funds to your account and try again.

DTS.Msg.CheckStatus.InvalidInitStatus

Scenario: You modify the objects to be synchronized.

Possible cause: The data synchronization task is not configured.

Solution: Complete the configurations of the data synchronization 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****')

Possible cause: The specified database account does not have the required permissions on the database.

DTS.Msg.DescribeColumns.TimeOut

Scenario: You query the information about columns in the source database, especially for a DTS task whose destination database is an AnalyticDB for MySQL database.

Possible 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 schemas of the source database times out.

DTS.Msg.DescribeStruct.TimeOut

Scenario: You query the information about the source database and tables in the source database after the connectivity test is passed.

Possible cause: You attempt to obtain the schemas of a large number of source databases. Alternatively, the source database has a large number of tables or is read at an excessively slow speed. As a result, the process of obtaining the schemas of the source database times out.

DTS.Msg.DRDSErrExecuteOnMySQL.ClientVersionTooLow

Scenario: You specify a PolarDB-X database as the source database of a DTS task.

Possible cause: The version of the PolarDB-X database client is earlier than required.

Solution: Update the PolarDB-X database client to a version that meets relevant requirements.

DTS.Msg.DbTypeNotSupport.OnlyReadRDS

Scenario: You specify a PolarDB-X database as the source database of a DTS task.

Possible 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

Scenario: You specify a PolarDB-X database as the source database of a DTS task.

Possible cause: The source database instance is a PolarDB-X instance whose storage type is PolarDB.

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

DTS.Msg.OperationDenied.NotPurchased

Scenario: You start a DTS task by calling an API operation.

Possible cause: No DTS instance is purchased for the DTS task that you attempt to start.

Solution: Purchase a DTS instance and then start the DTS task.

DTS.Msg.CheckJobFailed.ServerUnAvailable

Scenario: You configure a DTS task.

Possible 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 Alibaba Cloud technical support.

DTS.Msg.StopJobFailed.ServerUnAvailable

Scenario: You configure a DTS task.

Possible 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 Alibaba Cloud technical support.

DTS.Msg.SQLExecuteError.JDBC4CommunicationsException

Scenario: You query the information about the source database and tables in the source database after the connectivity test is passed.

Possible cause: An error occurs during data communication. A packet is sent from the Java Database Connectivity (JDBC) driver to the source database server, but no packet is received from the source database server.

DTS.Msg.SQLExecuteError.ConnectionRefused

Scenario: You query the information about the source database and tables in the source database after the connectivity test is passed.

Possible cause: Your request to connect to the source database is denied.

DTS.Msg.GetKafkaMetaInfo.NoAvailableBroker

Scenario: You set the Kafka Version parameter to Later Than 1.0 for the destination database.

Possible cause 1: You enter an invalid username or password of the database.

Solution: Enter the valid username and password. If authentication is disabled for the Kafka cluster, you do not need to enter the username and password.

Possible cause 2: You cannot obtain MetaInfo from the Kafka broker.

DTS.Msg.GetMongoDbShardInfo.EmptyInstances

Scenario: You specify an ApsaraDB for MongoDB (MongoDB) sharded cluster instance as the source or destination database of a DTS task.

Possible 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

Scenario: You specify a MongoDB sharded cluster instance as the source or destination database of a DTS task.

Possible 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

Scenario: You pause one or more DTS tasks at a time.

Possible cause: A DTS task is in the Modifying Objects state. To prevent data inconsistency, DTS does not allow you to pause a DTS task in the Modifying Objects state.

DTS.Msg.ModifyDenied.JobStatusNotRunning

Scenario: You modify the objects to be synchronized in a paused DTS task.

Possible cause: To prevent data inconsistency, DTS does not allow you to modify the objects to be synchronized in a paused DTS task. You are allowed to modify the objects to be synchronized when the state of the task is Running.

DTS.Msg.LXPayOrder.AmountLimitExceeded

Scenario: Payment cannot be made after you configure a DTS task.

Possible 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.

DTS.Msg.LXPayOrder.AccountBookNotExists

Scenario: Payment cannot be made after you configure a DTS task.

Possible cause: You do not add funds to your Alibaba Cloud account or your account balance is insufficient.

DTS.Msg.ConfigJob.NoneSelectedStep

Scenario: You call an API operation to configure a DTS task.

Possible cause: The type of the task is not configured. This indicates that the StructureInitialization, DataInitialization, and DataSynchronization parameters are all set to false.

Solution: Set these parameters to valid values to configure the type of the task.

DTS.Msg.ConfigJob.InvalidDbListFormat

Scenario: You call an API operation to configure a DTS task.

Possible cause: The value of the DbList parameter is an invalid JSON string.

Solution: Set this parameter to a valid JSON string.

DTS.Msg.ConfigJob.InvalidReserveFormat

Scenario: You call an API operation to configure a DTS task.

Possible cause: The value of the Reserve parameter is an invalid JSON string.

Solution: Set this parameter to a valid JSON string.

DTS.Msg.DistributedDatabaseNodesError

Scenario: You purchase a data synchronization instance and specify a distributed database as the source database.

Possible cause: The number of nodes of the distributed database is inconsistent with the value of the Number of Distributed Database Nodes parameter that you specify when you purchase the DTS instance.

Solution: You must set the Number of Distributed Database Nodes parameter to a value that is the same as the number of nodes of the distributed database.

DTS.Msg.LXQueryOrder.NotFoundNormalOrder

Possible cause 1: The instance is in the Completed state but is not released.

Solution: Release the instance that is in the Completed state.

Possible cause 2: The instance has been released but is still displayed in the DTS console.

Solution: Contact Alibaba Cloud technical support.

DTS.Msg.GetSSLInfo.NoSSLConn

Scenario: You select SSL-encrypted for the Encryption parameter when you configure a DTS task.

Possible cause: SSL encryption is disabled for the database instance that you configure.

Solution: Enable SSL encryption for the database instance, or set the Encryption parameter to Non-encrypted.

DTS.Msg.ModifyDynamicConfig.InvalidStatus

Scenario: You modify the configurations of a purchased data synchronization or data migration instance.

Possible 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

Possible cause: You perform the operation as a Resource Access Management (RAM) user, but the RAM user does not have the permissions to downgrade the configurations of a DTS instance.

Solution: Grant permissions to your RAM user and the corresponding Alibaba Cloud account to downgrade the configurations of a DTS instance. Contact Alibaba Cloud technical support.

DTS.Msg.OperationDenied.ConsumerGroupOutOfUsage

Scenario: You create a consumer group for a change tracking instance.

Possible cause: The change tracking instance 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

Scenario: You configure a DTS task.

Possible cause: An occasional error occurs.

Solution: Try again. If the error persists, contact Alibaba Cloud technical support.

DTS.Msg.DbListIsEmpty

Scenario: You call an API operation to configure a DTS task.

Possible cause: The DbList parameter is set to null, or the value of the parameter that you set is equivalent to null.

Solution: Set the DbList parameter to a value that is not null. For more information, see Objects of DTS tasks.

DTS.Msg.GetRedisNodes.NotCluster

Scenario: You specify an ApsaraDB for Redis (Redis) instance as the source or destination database of a DTS task.

Possible cause: The Instance Mode parameter is not configured based on the architecture of the Redis instance.

Solution: Configure the Instance Mode parameter based on the architecture of the Redis instance.

DTS.Msg.InvalidDestinationEndPointRegion

Scenario: You call an API operation to configure a DTS task.

Possible cause: You specify an invalid region or a region that is not supported by DTS for the destination database instance.

Solution: Specify a valid region for the destination database instance. For more information, see Supported regions.

DTS.Msg.InvalidSourceEndPointRegion

Scenario: You call an API operation to configure a DTS task.

Possible cause: You specify an invalid region or a region that is not supported by DTS for the source database instance.

Solution: Specify a valid region for the source database instance. For more information, see Supported regions.

DTS.Msg.AdminAccountExists

Scenario: You configure a DTS task.

Possible cause: DTS creates a privileged account for some types of source databases. If an existing account in the source database has the same name as the privileged account to be created by DTS, this error is reported.

Solution: Contact Alibaba Cloud technical support.

DTS.Msg.NotSupportModify

Scenario: You call the ModifyDtsJob operation to modify the configurations of a DTS task.

Possible cause: The DtsInstanceId parameter is set to the ID of a data migration instance.

Solution: You can modify only the extract, transform, and load (ETL) configurations of a data migration task in the DTS console. If you need to modify other configurations of a data migration task, you can create another task.

DTS.Msg.PrePayNotAllowDelete

Scenario: You call an API operation to release a DTS instance.

Possible cause: A subscription DTS instance cannot be released.

Solution: Do not release a subscription DTS instance.

DTS.Msg.Forbidden.AliyunUIDNotFound

Scenario: You configure a DTS task in the DTS console. This error often occurs if the task replicates data across Alibaba Cloud accounts or you log on to the DTS console as a RAM user.

Solution: View the unique ID (UID) in the error message, log on to the DTS console with the corresponding Alibaba Cloud account, and then try again.

DTS.Msg.RamPermissionDenied

Scenario: You log on to the DTS console as a RAM user to perform operations.

Possible cause: The RAM user does not have the required permissions.

DTS.Msg.EcsJoinSecurityGroupLimitExceeded

Scenario: You configure a DTS task in which the Access Method parameter is set to Self-managed Database on ECS for a database instance.

Possible cause: The ECS instance has been added to five security groups.

DTS.Msg.UpgradeTrialTimesLimit

Scenario: You experience a new feature provided by DTS to increase the maximum number of requests per second (RPS) for a DTS instance.

Possible cause: The trial quota for increasing the RPS upper limit is used up. DTS provides each Alibaba Cloud account with three times of free trial. Each time of free trial remains valid for 24 hours.

Solution: None.

DTS.Msg.HasRunningTrial

Scenario: You experience a new feature provided by DTS to increase the maximum number of RPS for a DTS instance.

Possible cause: The feature is enabled for the DTS instance. You cannot enable the feature for the DTS instance again when the previous time of free trial remains valid.

Solution: None.

DTS.Msg.DtsInstanceHasNoLimit

Scenario: You experience a new feature provided by DTS to increase the maximum number of RPS for a DTS instance.

Possible cause: The DTS instance has no RPS limits. Therefore, you cannot enable the feature for the DTS instance.

Solution: None.

DTS.Msg.UpgradeTrialInvalidJobStatus

Scenario: You experience a new feature provided by DTS to increase the maximum number of RPS for a DTS instance.

Possible cause: The feature is not supported for the DTS instance in the current state. This feature is supported only when the instance is in the Running, Paused, or Failed state.

Solution: None.

DTS.Msg.InvalidMigrationJobId

Scenario: You call an API operation to configure a DTS task.

Possible cause: You specify an invalid task ID, or the task is deleted.

Solution: Specify a valid task ID and try again.

DTS.Msg.InvalidIpAddress

Scenario: You configure a DTS task in which the Access Method parameter is set to Public IP Address, Express Connect, VPN Gateway, or Smart Access Gateway, or Cloud Enterprise Network (CEN) for a database instance.

Possible cause: The specified IP address is in an invalid format and therefore cannot be resolved.

Solution: Enter a valid IP address and try again.

DTS.Msg.PauseDenied.JobStatusNotRunning

Scenario: You pause a DTS task.

Possible cause: The task that you want to pause is not in the Running state. For example, the task may be in the Failed, Paused, or Initializing state.

Solution: Fix the task or wait until the task is in the Running state. Then, pause the task.

DTS.Msg.CheckpointOutOfAdjustableRange

Scenario: You modify the consumption checkpoint of the Incremental Write phase for a DTS instance.

Possible cause: The specified consumption checkpoint is not within the valid time range.

Solution: Specify a consumption checkpoint within the valid time range.

DTS.Msg.MaxRetryTime.Invalid

Scenario: You change the value of the Retry Time for Failed Connections parameter.

Possible cause: The new value is not within the valid value range. Valid values: 10 to 1440. Unit: minutes.

Solution: Specify a value within the valid value range for the Retry Time for Failed Connections parameter. We recommend that you set this parameter to a value greater than 30.

DTS.Msg.CrossRegionJobTransferToCluster

Scenario: You migrate a DTS task from a shared cluster to a dedicated cluster.

Possible cause: The source and destination databases that are specified in the DTS task in the shared cluster reside in different regions. In this case, you cannot migrate the DTS task to a dedicated cluster.

Solution: None.

DTS.Msg.JobNotInClusterRegion

Scenario: You migrate a DTS task from a shared cluster to a dedicated cluster.

Possible cause: The shared cluster from which you attempt to migrate the DTS task resides in a different region from the dedicated cluster. You can migrate the DTS task only to a dedicated cluster that resides in the same region as the shared cluster.

Solution: None.

DTS.Msg.CallCloudProductApiError

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS calls an API operation of another Alibaba Cloud service.

Solution: View the cause and solution based on the values of the CloudProduct, ErrCode, and ErrMsg parameters in the error message.

DTS.Msg.MongoCommandError

Scenario: You specify a MongoDB database as the source database of a DTS task.

Possible cause: An error occurs when you run MongoDB commands.

Solution: Refer to the official MongoDB documentation and troubleshoot the error based on the command that you run and the error message.

DTS.Msg.RedisCluster.NotSupportClassicNetworkEcs

Scenario: You specify a Redis database as the source or destination database of a DTS task by calling an API operation.

Possible cause: DTS does not support a Redis cluster that is hosted on an ECS instance deployed on the classic network.

Solution: None.

DTS.Msg.NotSupportRedisMinorVersion

Scenario: You specify a Redis database as the source or destination database of a DTS task by calling an API operation.

Possible cause: DTS does not support a Redis instance of the current minor version.

Solution: Update the minor version of the Redis instance and reconfigure the task. For more information about how to update the minor version, see Update the minor version of an instance.

DTS.Msg.DtsInstanceNotExists

Scenario: You call an API operation to query the details of a DTS instance.

Possible cause: The DTS instance does not exist.

Solution: None.

DTS.Msg.NotPurchaseDtsInstance

Scenario: You call an API operation to modify the throttling settings of a DTS task.

Possible cause: No DTS instance is purchased for the DTS task. You cannot modify the throttling settings.

Solution: Purchase a DTS instance and then modify the throttling settings.

DTS.Msg.NotSupportJobType

Scenario: You call an API operation to query the performance monitoring data.

Possible cause: DTS does not allow you to query the performance monitoring data for the current type of task.

Solution: None.

DTS.Msg.MysqlCommandError

Scenario: You run a MySQL command on a source or destination database.

Possible cause: An error occurs when you run the MySQL command.

Solution: Refer to the official MySQL documentation and troubleshoot the error based on the command that you run and the error message.

DTS.Msg.DynamicConfigError

Scenario: You modify the throttling settings of a DTS task.

Possible cause: The modification fails due to unstable network connections.

Solution: Try again.

DTS.Msg.GetVpcError

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS connects to a virtual private cloud (VPC)-connected instance.

Solution: Refer to the official VPC documentation and troubleshoot the error based on the error message.

DTS.Msg.ListResourceGroupsError

Scenario: You query the details of a DTS task.

Possible cause: An error occurs when DTS queries the resource group of the task.

Solution: Try again.

DTS.Msg.SearchDtsJobLogError

Scenario: You query the logs of a DTS task.

Possible cause: You specify an excessively large time range for the query.

Solution: Narrow down the time range of the query and try again.

DTS.Msg.GetDgInstanceError

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS connects to a database instance that is accessed by using a database gateway.

Solution: Refer to the official documentation of Database Gateway and troubleshoot the error based on the error message.

DTS.Msg.JobProgressNotExists

Scenario: You skip a table of the full data migration module.

Possible cause: An error occurs when you skip the table.

Solution: Try again.

DTS.Msg.GetCenError

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS connects to a CEN instance.

Solution: Refer to the official CEN documentation and troubleshoot the error based on the error message.

DTS.Msg.GetDgDatabaseError

Scenario: You configure a DTS task whose source or destination database instance is accessed by using a database gateway.

Possible cause: An error occurs when DTS connects to the database instance that is accessed by using a database gateway.

Solution: Contact Alibaba Cloud technical support.

DTS.Msg.SQLServerError

Scenario: You specify an SQL Server database as the source or destination database of a DTS task.

Possible cause: An error occurs when you execute an SQL statement.

Solution: Refer to the official SQL Server documentation and troubleshoot the error based on the statement that you execute and the error message.

DTS.Msg.InvalidDbList

Scenario: You modify the objects to be synchronized in a data synchronization task.

Possible cause: You specify an invalid parameter for the objects to be synchronized.

Solution: Make sure that the parameters of the objects to be synchronized are valid and try again.

DTS.Msg.GetRdsNetInfoError

Scenario: You specify an ApsaraDB RDS instance as the source or destination database of a DTS task.

Possible cause: An error occurs when DTS queries the network information of the ApsaraDB RDS instance.

Solution: Contact Alibaba Cloud technical support.

DTS.Msg.PolarDB.DBDescribeDBClusterAttribute

Scenario: You configure a DTS task whose source or destination database is a PolarDB instance, such as a PolarDB for MySQL, PolarDB for Oracle, PolarDB for PostgreSQL, or PolarDB-X instance.

Possible cause: An error occurs when DTS queries the information about the PolarDB instance.

Solution: Contact Alibaba Cloud technical support.

DTS.Msg.DgInstanceNotExists

Scenario: You configure a DTS task whose source or destination database instance is accessed by using a database gateway.

Possible cause: The database instance that is accessed by using a database gateway does not exist.

Solution: None.

DTS.Msg.MongoDB.DescribeDBInstanceAttribute

Scenario: You specify a MongoDB instance as the source or destination database of a DTS task.

Possible cause: An error occurs when DTS queries the information about the MongoDB instance.

Solution: Contact Alibaba Cloud technical support.

DTS.Msg.ClearConfigureContextError

Scenario: You modify the objects to be synchronized in a data synchronization task.

Possible cause: An error occurs when DTS modifies the objects to be synchronized.

Solution: Contact Alibaba Cloud technical support.

DTS.Msg.ModifyCheckpoint.CurrentCheckpointIsEmpty

Scenario: You modify the consumption checkpoint of a DTS task.

Possible cause: The specified consumption checkpoint is empty.

Solution: Check the specified consumption checkpoint and specify a consumption checkpoint within the valid time range.

DTS.Msg.DbInstanceNotExists

Scenario: You configure a DTS task.

Possible cause: The specified database instance does not exist.

Solution: None.

DTS.Msg.NotSupportEsInstance

Scenario: You configure a DTS task.

Possible cause: DTS does not support the current Elasticsearch cluster. An error occurs when DTS queries the network information of the Elasticsearch cluster.

Solution: Use an Elasticsearch cluster that is supported by DTS. For more information about the supported versions, see Overview of data synchronization scenarios and Overview of data migration scenarios.

DTS.Msg.AliyunDbsError

Scenario: You configure a data migration task whose source and destination SQL Server databases are accessed by using a physical protocol gateway.

Possible cause: An error occurs when you call an API operation to access Database Backup (DBS).

Solution: Troubleshoot the error based on the error message of the API operation.

DTS.Msg.ScheduleJobError

Scenario: You start, pause, or stop a DTS task.

Possible cause: DTS is temporarily unavailable.

Solution: Try again later.

DTS.Msg.InvalidPort

Scenario: You configure a DTS task.

Possible cause: The parameter that is used to specify the port number is invalid.

Solution: Enter a valid port number.

DTS.Msg.ModifyDtsJob.NoIncrementalWriteModule

Scenario: You modify the objects to be synchronized.

Possible cause: The current task is not a data synchronization task.

Solution: Check whether the task is a data synchronization task. You can modify the objects to be synchronized only for a data synchronization task.

DTS.Msg.ModifyDtsJob.HasCanNotRestartIncrementalWriteModule

Scenario: You modify the objects to be synchronized.

Possible cause: The incremental write module of the current task cannot be restarted.

Solution: Make sure that the incremental write module of the task is in the Running, Paused, or Failed state before you modify the objects to be synchronized.

DTS.Msg.ModifyDtsJob.HasNotSyncedIncrementalWriteModule

Scenario: You modify the objects to be synchronized.

Possible cause: The incremental write module of the current task is not running.

Solution: Make sure that the incremental write module of the task is in the Running state before you modify the objects to be synchronized.

Abnormal.RamCheckUserRole

Scenario: You create a DTS task.

Possible cause: The Alibaba Cloud account does not grant permissions to the AliyunDTSDefaultRole role that is the default role in DTS.

Solution: Grant permissions to the default role in DTS and try again. For more information about how to grant permissions, see Authorize DTS to access Alibaba Cloud resources.

Forbidden.InstanceNotFound

Scenario: You configure a DTS task.

Possible cause: The specified instance does not exist.

Solution: Make sure that the instance ID is valid and try again.

InvalidJobId

Scenario: You configure a DTS task.

Possible cause: The DTS task does not exist.

Solution: Make sure that the task ID is valid and try again.

InternalError

Scenario: You configure a DTS task.

Possible cause: A DTS internal error occurs.

Solution: Contact Alibaba Cloud technical support.

RdsGetInstanceAttr.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the information about an ApsaraDB RDS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

LXCreateOrder.InvokeFail

Scenario: You purchase a DTS instance.

Possible cause: An occasional error occurs.

Solution: Contact Alibaba Cloud technical support.

DbProductInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS calls an API operation of another Alibaba Cloud service.

Solution: Troubleshoot the error based on the error message returned by the API operation of another Alibaba Cloud service. If the error persists, contact Alibaba Cloud technical support.

InvalidParameter

Scenario: You call an API operation to configure a DTS task.

Possible cause: You specify an invalid parameter.

Solution: Set the parameter to a valid value.

DTS.Msg.CreateSubDistriubtedJobError

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS creates a distributed task.

Solution: Contact Alibaba Cloud technical support.

NotFound.UserDBInstanceList

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the details of database instances.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

AssumeRoleFail

Scenario: You configure a DTS task to replicate data across Alibaba Cloud accounts.

Possible cause: The name of the RAM role that you specify to access resources across Alibaba Cloud accounts is invalid.

Solution: Check whether the name of the RAM role is valid. For more information, see the Troubleshooting section of the "Synchronize data between ApsaraDB RDS for MySQL instances that belong to different Alibaba Cloud accounts" topic.

OperationDenied.JobStatus

Scenario: You configure a DTS task.

Possible cause: This operation is not allowed for the task in the current state.

Solution: Make sure that the state of the task meets relevant requirements and try again.

NetWorkItemNotFound

Scenario: You configure a DTS task.

Possible cause: The database instance does not support the specified network type.

Solution: Make sure that the specified network type is the same as the network type of the database instance.

EcsJoinSecurityGroup.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when an ECS instance is added to a security group.

Solution: Troubleshoot the error based on the error message. For more information, see the FAQ section of the Add a security group rule topic.

SQLExecuteError

Scenario: You configure a DTS task.

Possible cause: An error occurs when you execute an SQL statement.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

NoPermission

Scenario: You configure a DTS task as a RAM user.

Possible cause: The RAM user does not have the required permissions.

Solution: Grant the required 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.

PolarDbGetNetworkItems.InvokeFail

Scenario: You configure a DTS task whose source or destination database is a PolarDB instance, such as a PolarDB for MySQL, PolarDB for Oracle, PolarDB for PostgreSQL, or PolarDB-X instance.

Possible cause: An error occurs when DTS queries the information about the PolarDB instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

InvalidRpsValue

Scenario: You modify the throttling settings of a DTS task.

Possible cause: The specified RPS value does not meet relevant requirements.

Solution: Specify a valid RPS value based on the error message and try again.

RdsInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS calls an API operation of ApsaraDB RDS.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

InvalidTaskStatus

Scenario: You modify the objects to be synchronized.

Possible cause: The incremental write module of the current task is not running.

Solution: Make sure that the incremental write module of the task is in the Running state before you modify the objects to be synchronized.

PolarDbGetWhiteNames.InvokeFail

Scenario: You configure a DTS task whose source or destination database is a PolarDB instance, such as a PolarDB for MySQL, PolarDB for Oracle, PolarDB for PostgreSQL, or PolarDB-X instance.

Possible cause: An error occurs when DTS queries the whitelist information of the PolarDB instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

ADB30GetNetworkItems.InvokeFail

Scenario: You specify an AnalyticDB for MySQL V3.0 cluster as the destination database of a DTS task.

Possible cause: An error occurs when DTS queries the network information of the AnalyticDB for MySQL V3.0 cluster.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

QueryInstanceConnection

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the network information of a database instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

RdsGetInstanceList.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the details of ApsaraDB RDS instances.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

RdsGetWhiteNames.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the whitelist of an ApsaraDB RDS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

InvalidParameter.TagValue

Scenario: You add tags.

Possible cause: The value of a tag is invalid.

Solution: Specify a valid tag value and try again.

RamPermissionCheckFailed

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS checks the permissions of a RAM user.

Solution: Try again. If the error persists, contact Alibaba Cloud technical support.

RdsModifyWhiteName.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS modifies the whitelist of an ApsaraDB RDS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

DmsInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS calls an API operation of Data Management (DMS).

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

InvalidParameter.DStoreDataRange

Scenario: You modify the consumption checkpoint of a DTS task.

Possible cause: The specified consumption checkpoint is not within the valid time range.

Solution: Specify a consumption checkpoint within the valid time range based on the error message.

InvalidStepId

Scenario: You configure a DTS task.

Possible cause: The specified step does not exist.

Solution: Make sure that the step number is valid and try again.

IllegalJdbcUrl

Scenario: You configure a DTS task.

Possible cause: The JDBC URL of a database instance is invalid.

Solution: Use a valid JDBC URL and try again.

InvalidRegion.NotFound

Scenario: You configure a DTS task.

Possible cause: The region that you specify does not exist.

Solution: Specify a valid region and try again.

MissingParameter

Scenario: You configure a DTS task.

Possible cause: A required parameter is not specified in the request.

Solution: Make sure that the request parameters are valid and complete and try again.

AliyunProductInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS calls an API operation of another Alibaba Cloud service.

Solution: View the cause and solution based on the values of the CloudProduct, ErrCode, and ErrMsg parameters in the error message.

DTS.Msg.OperationDenied.JobStatus

Scenario: You configure a DTS task.

Possible cause: This operation is not allowed for the task in the current state.

Solution: Try again when the state of the task meets relevant requirements.

OperationDenied.DBInstanceStatus

Scenario: You configure a DTS task.

Possible cause: The ApsaraDB RDS instance that is configured for the task is not in the Running state.

Solution: Make sure that the state of the ApsaraDB RDS instance is Running. Try again later.

InvalidInstanceId

Scenario: You configure a DTS task.

Possible cause: The specified database instance does not exist.

Solution: Make sure that you specify a valid ID of the database instance and try again.

InvalidStepCode.NotAllowed

Scenario: You pause the incremental data collection module.

Possible cause: The incremental data collection module cannot be paused.

Solution: None.

InvalidJobType.NotToWay

Scenario: You reverse the direction of a two-way synchronization task.

Possible cause: The task of this type does not allow you to reverse the direction of synchronization.

Solution: None.

InvalidJobType.NotSupport

Scenario: You reverse the direction of a two-way synchronization task.

Possible cause: The task of this type does not allow you to reverse the direction of synchronization.

Solution: None.

InvalidJobStatus

Scenario: You reverse the direction of a two-way synchronization task.

Possible cause: The task in the current state does not allow you to reverse the direction of synchronization.

Solution: Make sure that the states of the forward and reverse synchronization tasks are Running or Paused. Then, try again.

HbaseueNetWorkItemNotFound

Scenario: You configure a DTS task.

Possible cause: The database instance does not support the specified network type.

Solution: Make sure that the specified network type is the same as the network type of the database instance.

InvalidSslConfig

Scenario: You configure a DTS task.

Possible cause: The SSL TrustStore file fails to be saved.

Solution: Try again. If the error persists, contact Alibaba Cloud technical support.

VpcInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS connects to a database instance.

Solution: Try again. If the error persists, contact Alibaba Cloud technical support.

QueryInstanceAttr

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the information about a database instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

QueryInstanceWhiteList

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the whitelist of a database instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

HbaseueModifyInstanceWhiteList

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the whitelist of a database instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

CreateAccountFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS creates a database account.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

ModifyAccountFail

Scenario: You configure a DTS task.

Possible cause: Permissions fail to be granted to a database account.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

DTS.Msg.ModifyDbListFail

Scenario: You modify the objects to be synchronized in a data synchronization task.

Possible cause: An error occurs when you modify the objects to be synchronized.

Solution: Try again. If the error persists, contact Alibaba Cloud technical support.

DropAccountFail

Scenario: You configure a DTS task.

Possible cause: A database account fails to be deleted.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

QueryAccountFail

Scenario: You configure a DTS task.

Possible cause: DTS fails to query a database account.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

AccountExists

Scenario: You configure a DTS task.

Possible cause: The specified database account already exists.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

RedisInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS calls an API operation of Redis.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

RedisError

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS connects to a Redis instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

DRDSInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS connects to a PolarDB-X 1.0 instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

DTS.Msg.InvalidDrdsTable

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the topology information of a table in a PolarDB-X 1.0 instance.

Solution: Make sure that the topology information of the table is valid based on the error message and try again. If the error persists, contact Alibaba Cloud technical support.

DTS.Msg.MissingUserName

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS verifies the AccessKey ID of the Alibaba Cloud account to which a MaxCompute project belongs.

Solution: Make sure that the AccessKey ID of the Alibaba Cloud account is valid and try again.

DTS.Msg.MissingPassword

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS verifies the AccessKey secret of the Alibaba Cloud account to which a MaxCompute project belongs.

Solution: Make sure that the AccessKey secret of the Alibaba Cloud account is valid and try again.

PolarDbInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the information about a database instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

GpdbInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the information about a database instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

EcsInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the information about a database instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

AdsV3InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the information about a database instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

DTS.Msg.InvalidDbListError

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS verifies the objects to be synchronized.

Solution: Make sure that the objects to be synchronized are properly configured and try again.

ADB30GetWhiteNames.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the whitelist information of an AnalyticDB for MySQL V3.0 cluster.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

ADB30ModifyWhiteName.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS modifies the whitelist of an AnalyticDB for MySQL V3.0 cluster.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

ADB30GetInstanceList.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the details of AnalyticDB for MySQL V3.0 clusters.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

ADB30GetDbClusterAttr.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the information about an AnalyticDB for MySQL V3.0 cluster.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

DescribeResourceUsage.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the resource usage information of an ApsaraDB RDS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

DescribeDatabases.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the information about an ApsaraDB RDS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

RdsGetInstanceConnection.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the connection information of an ApsaraDB RDS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

RdsCreateUserAccount.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS creates a database account for an ApsaraDB RDS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

RdsGetNetworkItems.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the connection information of an ApsaraDB RDS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

HbaseueGetNetworkItems.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the connection information of an ApsaraDB for HBase instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

GetNetworkItems.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the connection information of a database.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

RdsGetRegions.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the region information of an ApsaraDB RDS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

RdsCreateMigrateTask.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS creates a data migration task whose source or destination database is an ApsaraDB RDS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

RdsDescribeMigrateTaskById.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries a data migration task whose source or destination database is an ApsaraDB RDS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

MongoDbGetWhiteNames.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the whitelist information of a MongoDB instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

MongoDbGetInstanceList.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the details of MongoDB instances.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

MongoDbGetInstanceConnection.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the connection information of a MongoDB instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

MongoDbGetShardingMongoConnection.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the connection information of a shard node in a MongoDB instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

MongoDbModifyWhiteNames.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS modifies the whitelist of a MongoDB instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

MongoDbGetInstanceAttr.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the information about a MongoDB instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

MongoDbGetShardingMongoGidInvokeFail.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the gid parameter of a shard node in a MongoDB instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

PolarDbGetInstanceList.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the details of PolarDB instances.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

PolarDbGetInstanceConnection.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the connection information of a PolarDB instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

PolarDbModifyWhiteNames.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS modifies the whitelist of a PolarDB cluster.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

PolarDbGetInstanceAttr.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the information about a PolarDB instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

RedisGetWhiteNames.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the whitelist information of a Redis instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

RedisGetInstanceList.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the details of Redis instances.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

RedisGetInstanceConnection.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the connection address of a Redis instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

RedisModifyWhiteNames.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS modifies the whitelist of a Redis instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

RedisGetInstanceAttr.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the information about a Redis instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

RedisGetNetworkItems.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the connection address of a Redis instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

RedisCreateAccount.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS creates a database account for a Redis instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

RedisGetComputingType.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the architecture of a Redis instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

EcsGetWhiteNames.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the whitelist of an ECS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

EcsGetInstanceList.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the details of ECS instances.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

EcsGetMetricList.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the metrics of an ECS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

EcsGetInstanceConnection.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the network information of an ECS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

EcsModifySecurityGroup.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS changes the security group of an ECS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

EcsAuthSecurityGroup.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS accesses the security group of an ECS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

EcsLeaveSecurityGroup.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when an ECS instance is removed from a security group.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

EcsGetInstanceAttr.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the information about an ECS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

EcsGetSecurityGroupAttr.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the security group of an ECS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

EcsDelSecurityGroup.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when an ECS security group is deleted.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

EcsRevokeSecurityGroup.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when an ECS security group is deleted.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

EcsGetNetworkItems.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the security group rules of an ECS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

EcsCreateAccount.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS creates an account for an ECS instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

LindormGetNetworkItems.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the connection information of a Lindorm instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

LindormGetVpcAddress.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the connection information of a Lindorm instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

LindormGetInstanceAttr.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the information about a Lindorm instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

InvalidOperation.AdvanceAction

Scenario: You modify the consumption checkpoint of a DTS task.

Possible cause: The task does not have the incremental data collection module. The consumption checkpoint cannot be modified.

Solution: None.

TablestoreInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS queries the information about a database instance.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

UnSupported

Scenario: You configure a DTS task.

Possible cause: The task does not support this operation.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

UnSupportedTaskType

Scenario: You configure a DTS task.

Possible cause: The task of this type does not support this operation.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

CheckJobCreateFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS creates a verification task.

Solution: Try again. If the error persists, contact Alibaba Cloud technical support.

ConfigurationDtsJobFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS creates a DTS task whose source or destination database is a DB2 for i (AS/400) database.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

AllSiteInnerApiSupportFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS creates a database account.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

Missing.TagKey

Scenario: You add tags to one or more DTS instances.

Possible cause: No tag key is specified for a tag.

Solution: Specify a valid tag key and try again.

MissingParameter.TagOrResourceId

Scenario: You call an API operation to add tags to one or more DTS instances.

Possible cause: No instance ID, tag key, or tag value is specified in the input parameters.

Solution: Make sure that the input parameters are valid and complete and try again.

InvalidParameter.ResourceType

Scenario: You call an API operation to query or add tags.

Possible cause: The value of the ResourceType parameter is invalid.

Solution: Set the ResourceType parameter to ALIYUN::DTS::INSTANCE and try again.

InvalidParameter.TagKey

Scenario: You call an API operation to query or add tags.

Possible cause: The key of a tag is invalid.

Solution: Specify a valid tag key and try again.

InvalidResourceId.NotFound

Scenario: You call an API operation to query or add tags.

Possible cause: The specified DTS instance does not exist.

Solution: Make sure that the ResourceId parameter is valid and try again.

InvalidParameter.Tags

Scenario: You call an API operation to query or add tags.

Possible cause: The key or value of a tag is invalid.

Solution: Specify a valid key and value for the tag and try again.

InvalidParameter.NextToken

Scenario: You call an API operation to query or add tags.

Possible cause: An error occurs when DTS parses a tag.

Solution: Try again. If the error persists, contact Alibaba Cloud technical support.

InvalidParameter.Category

Scenario: You call an API operation to query all tags.

Possible cause: The Category parameter is invalid.

Solution: Set the Category parameter to Custom if the tag is custom or System if the tag is provided by DTS. Then, try again.

NumberExceed.Tags

Scenario: You add tags to one or more DTS instances.

Solution: Reduce the number of tags and try again.

NumberExceed.ResourceIds

Scenario: You add tags to one or more DTS instances.

Solution: Reduce the number of instances and try again.

Duplicate.TagKey

Scenario: You add tags to one or more DTS instances.

Possible cause: A tag already exists.

QuotaExceed.TagsPerResource

Scenario: You add tags to one or more DTS instances.

Solution: Remove the tags that are no longer used on the premise that your business is not affected. Then, try again.

NoPermission.SystemTag

Scenario: You add tags to one or more DTS instances.

Possible cause: An error occurs when DTS queries tags.

Solution: Contact Alibaba Cloud technical support.

NoPermission.Operator

Scenario: You add tags to one or more DTS instances.

Possible cause: An error occurs when DTS queries tags.

Solution: Contact Alibaba Cloud technical support.

UnsupportedTaskRegion

Scenario: You configure tasks in a dedicated cluster.

Possible cause: Dedicated clusters do not support DTS tasks that are configured to migrate or synchronize data across regions.

Solution: None.

UnsupportedDtsJob

Scenario: You configure tasks in a dedicated cluster.

Possible cause: The task does not support this operation.

Solution: None.

UnsupportedDtsInstance

Scenario: You configure tasks in a dedicated cluster.

Possible cause: The DTS instance does not support dedicated clusters.

Solution: None.

UnsupportedTransferType

Scenario: You configure tasks in a dedicated cluster.

Possible cause: DTS does not support tasks that migrate data across dedicated clusters.

Solution: None.

DedicatedClusterReleased

Scenario: You configure tasks in a dedicated cluster.

Possible cause: The dedicated cluster is released.

Solution: None.

DedicatedClusterReleasing

Scenario: You configure tasks in a dedicated cluster.

Possible cause: The dedicated cluster is being released.

Solution: None.

OperationDenied.DedicatedClusterStatus

Scenario: You configure tasks in a dedicated cluster.

Possible cause: The dedicated cluster is not in the Running state.

Solution: None.

OperationDenied.DedicatedClusterUsedDu

Scenario: You configure tasks in a dedicated cluster.

Possible cause 1: The remaining available DTS units (DUs) in the dedicated cluster are insufficient.

Possible cause 2: The specified dedicated cluster does not exist.

Solution: Purchase a dedicated cluster and try again. For more information, see Create a DTS dedicated cluster.

DedicatedClusterAllocateDuFail

Scenario: You configure tasks in a dedicated cluster.

Possible cause: An error occurs when the dedicated cluster allocates DUs.

Solution: Try again. If the error persists, contact Alibaba Cloud technical support.

JobProgressNotFound

Scenario: You skip a table during full data migration.

Possible cause: The full data migration task that contains the table does not exist.

Solution: None.

LXBuyError

Scenario: You purchase a DTS instance.

Possible cause: An error occurs when you purchase the instance.

Solution: Try again. If the error persists, contact Alibaba Cloud technical support.

SourceIpIsNotAllowedToConnect

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS verifies the public IP address of the source database.

Solution: Try again. If the error persists, contact Alibaba Cloud technical support.

DestIpIsNotAllowedToConnect

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS verifies the public IP address of the destination database.

Solution: Try again. If the error persists, contact Alibaba Cloud technical support.

MissingDtsInstanceId

Scenario: You configure a DTS task.

Possible cause: No DTS instance ID is specified in the request parameters.

Solution: Check whether the request parameters are valid.

RgPreCheckFailed

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS checks the resource group of the task.

Solution: Contact Alibaba Cloud technical support.

RgOperationFailed

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS checks the resource group of the task.

Solution: Try again. If the error persists, contact Alibaba Cloud technical support.

RgRegionNotSupport

Scenario: You configure a DTS task.

Possible cause: An error occurs when DTS checks the resource group of the task.

Solution: Try again. If the error persists, contact Alibaba Cloud technical support.

MissingDestinationEndpointPort

Scenario: You configure a DTS task.

Possible cause: No port is specified for the destination database in the request parameters.

Solution: Make sure that the request parameters are valid and complete and try again.

MissingSourceEndpointPort

Scenario: You configure a DTS task.

Possible cause: No port is specified for the source database in the request parameters.

Solution: Make sure that the request parameters are valid and complete and try again.

DTS.Msg.NotSupportSubscribeJob

Scenario: You modify a change tracking task in the DTS console of the new version.

Possible cause: The change tracking task is created in the DTS console of the previous version. You cannot modify this task in the DTS console of the new version.

Solution: Modify the change tracking task in the DTS console of the previous version. You can go back to the DTS console of the previous version by performing the following steps: Go to the Change Tracking page in the DMS console, move the pointer over the icon in the lower-right corner and click the icon. You are navigated to the DTS console of the previous version.

DTS.Msg.VpcSubnetIpExhaust

Scenario: You create a consumer group for a change tracking task.

Possible cause: The number of available IP addresses of the vSwitch configured for the task is insufficient.

Solution: Make sure that the number of available IP addresses of the vSwitch is sufficient, and try again. If the error persists, contact Alibaba Cloud technical support.

DTS.Msg.GetCenVpcError

Scenario: You configure a DTS task whose source or destination database instance is accessed by using a CEN instance.

Possible cause: An error occurs when DTS queries the VPCs that are attached to the CEN instance.

Solution: Make sure that the specified CEN instance ID is valid and try again. If the error persists, contact Alibaba Cloud technical support.

DTS.Msg.InvalidMongoDBStatus

Scenario: You specify a MongoDB instance as the source or destination database of a DTS task.

Possible cause: The MongoDB instance is invalid.

Solution: Check the status of the MongoDB instance, wait until the MongoDB instance properly runs, and then try again.

SQLException: Misconfigured master - master server_id is 0

Scenario: You configure a DTS task.

Possible cause: The server_id parameter of the source database fails to pass the verification.

Solution: Set the server_id parameter to an integer that is greater than 1 and is not the same as that of any other database, and then try again. For more information, see Value of server_id in the source database.

Common errors that may be returned when a DTS task is running

DTS-RETRY-ERR-0001: get table (.*)? detail info failed (.*)? Table (.*)? doesn't exist

Possible cause: When you configure a data migration or synchronization task, you do not select Schema Migration or Schema Synchronization as a migration or synchronization type. In addition, in the destination database, you do not create a table that has the same schema as the table mentioned in the error message in the source database. As a result, the corresponding table does not exist in the destination database.

replicate-mysql: DTS-70002: get table [dts_order] detail info failed.\ncause:\n\tMySQLSyntaxErrorException: 
Table 'dts_order' doesn't exist

DTS-RETRY-ERR-0002: get table (.*)? detail info failed (.*)? Table (.*)? does not exist

Possible cause: Some tables do not exist in the source or destination database.

replicate-mysql: DTS-70002: get table [ars_uat.immc_mc_cs_clue_order] detail info failed.\ncause:\n\tMySQLSyntaxErrorException: Table 'ars_uat.immc_mc_cs_clue_order' doesn't exist

DTS-RETRY-ERR-0003: get table (.*)? detail info failed (.*)? connect target failed (.*)? Access denied for user

Possible cause: The account information that is configured in a task to connect to the destination database is modified when the task is running. As a result, the destination database cannot be connected. For example, you may modify the account password or permissions or delete the account when the task is running.

replicate-mysql: DTS-70002: get table [db_yfq.czb_oil_station] detail info failed.\ncause:\n\tDBCommonException: 
replicate-mysql: DTS-71016: connect target failed (url: jdbc:mysql://121.36.XX.XX:XXXX?useSSL=false&useUnicode=true
&characterEncoding=utf8&rewriteBatchedStatements=true&allowMultiQueries=true&zeroDateTimeBehavior=convertToNull&
autoReconnect=false&failOverReadOnly=false&useLocalSessionState=true&transformedBitIsBoolean=FALSE&tinyInt1isBit=
FALSE&sessionVariables=sql_mode=''&allowLoadLocalInfile=true&allowPublicKeyRetrieval=true&socketTimeout=3600000&
connectTimeout=3600000)\n\tSQLException: Access denied for user 'root'@'8.131.XX.XX' (using password: YES)

DTS-RETRY-ERR-0004: get table (.*)? detail info failed (.*)? No worker nodes available in resource group

Possible cause: When DTS obtains the schema of the specified table, no worker node is available in the AnalyticDB for MySQL database.

Solution: Check whether the AnalyticDB for MySQL database has available worker nodes.

id=34284****, jobId=cvft576n24l9****, value={"errMsg":"replicate-adb30: DTS-70002: get table [mgdevsys.mytable] 
detail info failed.\ncause:\n\tSQLException: [31003, 2022110109452317201617024803453049329] : No worker nodes 
available in resource group ","jobId":"cfal5qfd243d834","maxRetryTime":7200,"module":"writer","retryCount":2,
"retryTarget":"destDB","retryTime":132,"retrying":true}

DTS-RETRY-ERR-0006: Can not find column (.*)? in destination table

Possible cause: A column is not found in the destination table.

framework: DTS-30019: Can not find column \"wx_state\" in destination table \"dts_user_authorization\". 
Please add the column in the destination table.

What to do next: DTS cannot synchronize DDL operations. Therefore, if you add a column to a table in the source database during data synchronization, this error occurs. In this case, add the column to the destination table before you add the column to the source table. This prevents the error.

DTS-RETRY-ERR-0007: Failed to get offsets by times in (.*)? ms

Possible cause 1: The connection between the data write module and the data cache module times out due to network jitters.

Solution: Restart the task and check whether the task can be resumed.

Possible cause 2: The task is delayed for an extended period of time.

Solution: The task cannot be resumed and you must reconfigure the task. To do so, choose > Reconfigure Task in the Actions column of the instance to which the task belongs.

Failed to get offsets by times in 60000 ms

DTS-RETRY-ERR-0008: Failed to seek oracle position

Possible cause: The relevant logs cannot be found because the logs in the source database are cleared.

Solution: Reconfigure the task.

dts-k-src: DTS-52110: OracleRecordExtractor Init Error: oracle-reader: DTS-52061: Failed to seek oracle position

DTS-RETRY-ERR-0010: execute statement failed (.*)? modify precision is not supported

Possible cause: DTS does not support relevant DDL statements in data synchronization scenarios. As a result, the DDL statements fail to be executed.

transaction-replicate: DTS-70004: execute statement failed: /* dts_id=dtsit911vn1255**** */alter table `billing`.`store_payroll_detail` modify column `epidemic_subsidy` DECIMAL(20, 5) comment '****'
cause:
    SQLException: [15018, 202210211956001921681171220345323****] modify precision is not supported, col=epidemic_subsidy, type decimal, old=21, new=20

DTS-RETRY-ERR-0011: seek timestamp for topic (.*)? with position (.*)? failed

Possible cause 1: The task is paused for an extended period of time. After you restart the task, the data cache module has no data at a specific consumption checkpoint.

Possible cause 2: The task failed for an extended period of time. After you fix the issue, the data cache module has no data at a specific consumption checkpoint.

Solution: Create another task. Before you create the task, evaluate the amount of data to be migrated or synchronized. If the amount of data is large, we recommend that you create multiple tasks.

capture-dstore: DTS-50019: seek timestamp for topic [cn_hangzhou_vpc_rm_XXXX_version2-0] 
with position [{"timestamp":1660802171, "offset":-1}] failed

DTS-RETRY-ERR-0012: execute statement failed (.*)? modify column type is not supported

Possible cause: DTS does not support relevant DDL statements in data synchronization scenarios. As a result, the DDL statements fail to be executed.

transaction-replicate: DTS-70004: execute statement failed: /* dts_id=dtsit911vn1255**** */alter table `billing`.`store_payroll_detail` modify column `epidemic_subsidy` DECIMAL(20, 5) comment '****'
cause:
    SQLException: [15018, 202210211956001921681171220345323****] modify precision is not supported, col=epidemic_subsidy, type decimal, old=21, new=20

DTS-RETRY-ERR-0013: execute statement failed (.*)? command denied to user

Possible cause: The account of the destination database does not have the required permissions.

Solution: Check the permissions of the account of the destination database and grant the permissions mentioned in the error message to the account.

id=34286****, jobId=g5lw9b3121v****, value={"errMsg":"transaction-replicate: DTS-70004: execute statement failed: 
null\ncause:\n\tMySQLSyntaxErrorException: INSERT, UPDATE command denied to user 'dts_customerczd'@'172.17.XX.XX' 
for table 'dts_trx4unit_mark_18'","jobId":"bh2u9v80213****","maxRetryTime":7200,"module":"writer","retryCount":35,
"retryTarget":"destDB","retryTime":372,"retrying":true}

DTS-RETRY-ERR-0015: execute statement failed (.*)? Invalid object name

Possible cause: The table mentioned in the error message does not exist in the destination database.

id=344846732, jobId=ymp1082920y****, value={"errMsg":"replicate-sqlserver: DTS-70002: get table [[test].[dbo].[task]] 
detail info failed.\ncause:\n\tSQLServerException: Invalid object name 'test.dbo.task'.","jobId":"anv103sx20od235",
"maxRetryTime":86400,"module":"writer","retryCount":345,"retryTarget":"destDB","retryTime":3458,"retrying":true}

DTS-RETRY-ERR-0016: execute statement failed (.*)? elasticsearch (.*)? ResponseException (.*)? SERVICE_UNAVAILABLE

Possible cause: The destination Elasticsearch service is unavailable.

Solution: Check whether the destination Elasticsearch service is available.

{"errMsg":"transaction-replicate: DTS-70004: execute statement failed: null\ncause:\n\tSQLException: 3: meet error, 
updateSQL **** error detail message:org.elasticsearch.client.ResponseException: **** 503\n}\n\n\tSQLException: org.
elasticsearch.client.ResponseException: ****}

DTS-RETRY-ERR-0018: read source data error (.*)? Error retrieving record (.*)? Can not read response from server

Possible cause: DTS fails to connect to the database.

Solution: Check whether the database can be connected and restart the task. For more information, see Source database connectivity and Destination database connectivity.

id=34281****, jobId=n9f10m6i28s3601, value={"errMsg":"framework: DTS-31009: read source data error\ncause:\n\
tSQLException: Error retrieving record: Unexpected Exception: java.io.EOFException message given: Can not read 
response from server. Expected to read 987 bytes, ****}

DTS-RETRY-ERR-0019: read source data error (.*)? Error retrieving record (.*)? Connection reset

Possible cause: The database connection is reset.

Solution: Check the network connection and test whether the database can be connected.

id=34289****, jobId=n9f10m6i28s****, value={"errMsg":"framework: DTS-31009: read source data error\ncause:
\n\tSQLException: Error retrieving record: Unexpected Exception: java.net.SocketException message given: 
Connection reset\n\nNested Stack Trace:\n\n\n** BEGIN NESTED EXCEPTION ** \n\njava.net.SocketException\nMESSAGE: 
Connection reset\n\nSTACKTRACE:\n\njava.net.SocketException: Connection reset\n\tat java.net.SocketInputStream.
read(SocketInputStream.java:210)\n\tat java.net.SocketInputStream.read(SocketInputStream.java:141)\n\tat com.mysql.
cj.protocol.ReadAheadInputStream.fill(ReadAheadInputStream.java:107)\n\tat com.mysql.cj.protocol.ReadAheadInputStream.
readFromUnderlyingStreamIfNecessary(ReadAheadInputStream.java:150)\n\tat com.mysql.cj.protocol.ReadAheadInputStream.
read(ReadAheadInputStream.java:180)\n\tat java.io.FilterInputStream.read(FilterInputStream.java:133)\n\tat com.mysql.
jdbc.MySQLInputNetIoStream.read(MySQLInputNetIoStream.java:29)\n\tat java.io.FilterInputStream.read(FilterInputStream.
java:133)\n\tat com.mysql.cj.protocol.FullReadInputStream.readFully(...","jobId":"ga310k47281****","maxRetryTime":
7200,"module":"full","retryCount":3,"retryTarget":"srcDB","retryTime":15445,"retrying":true}

DTS-RETRY-ERR-0020: read source data error (.*)? Table (.*)? is marked as crashed and should be repaired

Possible cause: The index of a table in the source database is damaged. As a result, data cannot be read from the table.

Solution: Repair the index of the table based on the error message.

framework: DTS-31009: read source data error\ncause:\n\tSQLException: 
Table 'mytable' is marked as crashed and should be repaired

use my_database;
repair table mytable;

DTS-RETRY-ERR-0021: BatchUpdateException (.*)? no this column (.*)? in this table

Possible cause: A column does not exist in the destination table.

Solution: Add the missing column to the destination table and restart the task.

id=34293****, jobId=zjj11te2w1i****, value={"errMsg":"java.sql.BatchUpdateException: [13000, 202211011449191921681280300345301****] 
syntax error :no this column => __dts_data_source, in this table LY.C1","jobId":"gqy11x78c19****","maxRetryTime":7200,"module":"full",
"retryCount":485,"retryTarget":"destDB","retryTime":4848,"retrying":true}

DTS-RETRY-ERR-0024: disk usage exceeded flood-stage watermark

common: DTS-11005: es: DTS-10035: index [tp_adlist_day_report_11] blocked by: [TOO_MANY_REQUESTS/12/disk usage 
exceeded flood-stage watermark, index has read-only-allow-delete block];\ncause:\n\tIOException: es: DTS-10035: 
index [tp_adlist_day_report_11] blocked by: [TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index 
has read-only-allow-delete block];\n\tCriticalAnyAllException: es: DTS-10035: index [tp_adlist_day_report_11] 
blocked by: [TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];

DTS-RETRY-ERR-0025: disk is over flow

common: DTS-11005: es: DTS-10035: index [tp_adlist_day_report_11] blocked by: [TOO_MANY_REQUESTS/12/disk usage 
exceeded flood-stage watermark, index has read-only-allow-delete block];\ncause:\n\tIOException: es: DTS-10035: 
index [tp_adlist_day_report_11] blocked by: [TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index 
has read-only-allow-delete block];\n\tCriticalAnyAllException: es: DTS-10035: index [tp_adlist_day_report_11] 
blocked by: [TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];

DTS-RETRY-ERR-0026: connect timed out

Possible cause: DTS fails to connect to the database.

Solution: Check whether the database can be connected and restart the task. For more information, see Source database connectivity and Destination database connectivity.

java.net.SocketTimeoutException: connect timed out@error code:1042

DTS-RETRY-ERR-0027: Communications link failure (.*)? The driver has not received any packets from the server

Possible cause 1: The database is connected to DTS as a self-managed database. However, the address or port number of the database is incorrectly configured.

Solution: Check and correct the address and port number of the database, and then restart the task.

Possible cause 2: The database is connected to DTS by using Express Connect. However, an exception occurs on the Express Connect circuit.

Solution: Check the route table and firewall configurations for the Express Connect circuit.

Communications link failure\n\nThe last packet sent successfully to the server was 0 milliseconds ago. The driver 
has not received any packets from the server.@error code:0

DTS-RETRY-ERR-0028: UnknownHostException (.*)? aliyuncs\\.com

Possible cause: The destination database instance is released.

Solution: The task cannot be resumed. Reconfigure the task.

java.net.UnknownHostException: rm-bp167dm72ah1hm1****.mysql.rds.aliyuncs.com@error code:1042

DTS-RETRY-ERR-0029: Too many connections (.*)? error code

Possible cause: The number of database connections has reached the upper limit.

Solution: Increase the maximum number of connections to the database and restart the task.

Too many connections@error code:1040

DTS-RETRY-ERR-0030: ConnectException (.*)? Connection refused

Possible cause: The connection request from DTS is rejected.

Solution: Check the blacklist and whitelist of the database.

id=34269****, jobId=pfi10xxa251****, value={"errMsg":"java.net.ConnectException: Connection refused (Connection refused)@error code:1042","jobId":"ehz1066b257****","maxRetryTime":43200,"module":"reader","retryCount":3,"retryTarget":"srcDB","retryTime":30,"retrying":true}

DTS-RETRY-ERR-0032: SQLServerException (.*)? The connection is closed

Possible cause: The connection to the source or destination SQL Server database is closed.

Solution: Make sure that the source or destination SQL Server database can be connected, and restart the task.

java.lang.RuntimeException: com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed.

DTS-RETRY-ERR-0033: SQLServerException (.*)? Connection reset

Possible cause: The network is unstable, and the database connection is reset.

Solution: Make sure that the source or destination SQL Server database can be connected, and restart the task.

id=34271****, jobId=c2x10019318****, value={"errMsg":"com.microsoft.sqlserver.jdbc.SQLServerException: Connection 
reset ClientConnectionId:8a2bcd3d-3a6f-4b06-b5c4-94944d40****","jobId":"al9105f2314****","maxRetryTime":7200,"module":
"writer","retryCount":2,"retryTarget":"destDB","retryTime":28,"retrying":true}

DTS-RETRY-ERR-0034: elasticsearch (.*)? ResponseException (.*)? Too Many Requests

Possible cause: The connection to the Elasticsearch service is abnormal.

Solution: Check whether the Elasticsearch service is accessible and restart the task.

common: DTS-11005: org.elasticsearch.client.ResponseException: POST http://172.16.XX.XX:XXXX/_bulk?pretty=true: HTTP/1.1 429 
Too Many Requests ****

DTS-RETRY-ERR-0035: Your password has expired

Possible cause: The password that is used in the DTS task has expired.

Your password has expired. To log in you must change it using a client that supports expired passwords.@error code:1862

DTS-RETRY-ERR-0036: Can't use (.*)? database through mongos (.*)? on server

Possible cause 1: The MongoDB database account that is used by the DTS task does not have the required permissions.

Solution: Grant permissions to the database account based on the error message and restart the task.

Possible cause 2: The data to be synchronized or migrated is in the admin or local database.

Solution: You cannot synchronize or migrate data from the admin or local database.

Command failed with error 20 (IllegalOperation): 'Can't use 'local' database through mongos' on server s-
bp1698827e718b84-pub.mongodb.rds.aliyuncs.com:3717.

DTS-RETRY-ERR-0037: The last packet sent successfully to the server was (.*)? milliseconds ago

Possible cause: DTS fails to connect to the database.

Solution: Check whether the database can be connected and restart the task. For more information, see Source database connectivity and Destination database connectivity.

id=342986938****, jobId=iv6a9w5za8****, value={"errMsg":"com.mysql.cj.exceptions.CJCommunicationsException: The 
last packet successfully received from the server was 1 milliseconds ago.  The last packet sent successfully to 
the server was 14,513,692,650 milliseconds ago. ****

DTS-RETRY-ERR-0038: Statement cancelled due to timeout or client request

Possible cause: The SQL query times out when DTS queries the latest consumption checkpoint of the binary logs of the source database.

Solution: Make sure that DTS can connect to the source database and restart the task.

id=34289****, jobId=lv710sub15r****, value={"errMsg":"Statement cancelled due to timeout or client request@error code:0","jobId":"wig100eq157****","maxRetryTime":43200,"module":"reader","retryCount":4,"retryTarget":"srcDB","retryTime":520,"retrying":true}

DTS-RETRY-ERR-0039: Connect db failure (.*)? connect timed out

Possible cause: The connection to a database times out.

Solution: Make sure that DTS can connect to the database and restart the task.

id=34284****, jobId=dv9w1fpej7j****, value={"errMsg":"DTS-002003 Connect db failure, unknow db url 100.100.XX.XX:XXX, please vaild url. Original error: java.net.SocketTimeoutException: connect timed out For more information please refer to https://****/document_detail/****.htm","jobId":"rcxy3zwo164****","maxRetryTime":43200,"module":"reader","retryCount":0,"retryTarget":"dstore","retryTime":19851828,"retrying":true}

DTS-RETRY-ERR-0040: Verify the connection properties and check that an instance of SQL Server is running on the host

Possible cause: The connection to a database fails.

Solution: Make sure that DTS can connect to the database and restart the task.

id=34286****, jobId=hy0s8l20276****, value={"errMsg":"The TCP/IP connection to the host 172.26.XX.XX, port 51808 has failed. Error: \"The driver received an unexpected pre-login response. Verify the connection properties and check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. This driver can be used only with SQL Server 2005 or later.\". ClientConnectionId:f8d40feb-1345-4064-82d8-fe4e2893****@error code:0","jobId":"g5bf870q27b****","maxRetryTime":7200,"module":"reader","retryCount":1,"retryTarget":"srcDB","retryTime":15,"retrying":true}

DTS-RETRY-ERR-0041: Error on Send (.*)? Expiring (.*)? has passed since batch creation plus linger time

Possible cause: The incremental data collection module is abnormal.

Solution: Restart the incremental data collection module.

id=34286****, jobId=ehi11j9jw1h****, value={"errMsg":"dts-k-src: DTS-52122: Error on Send.Expiring 4251 record(s) for ap_southeast_1_vpc_rm_t4npvr5594z735ic5_imi_sg_prod_version2-0: 180182 ms has passed since batch creation plus linger time","jobId":"s3c116i9z1t****","maxRetryTime":7200,"module":"reader","retryCount":0,"retryTarget":"dstore","retryTime":1,"retrying":true}

DTS-RETRY-ERR-0042: No operations allowed after statement closed

Possible cause: The connection to the destination database fails.

Solution: Make sure that DTS can connect to the destination database and restart the task.

id=34284****, jobId=d3a107cy29z****, value={"errMsg":"framework: DTS-30011: currentRunningSQL: /* DTS-full-g86108c2294**** */insert ignore into `mpm_workflow`.`tb_conn_log_archive`(`conn_type`,`creator_user_id`,`call_class`,`create_time`,`recall_method`,`header_json`,`url`,`times`,`creator_user_name`,`response`,`success`,`id`,`last_mod_time`,`request_data`) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?), reason: No operations allowed after statement closed.\ncause:\n\tSQLException: No operations allowed after statement closed.\n\tStatementIsClosedException: No operations allowed after statement closed.","jobId":"g86108c2294****","maxRetryTime":7200,"module":"full","retryCount":8,"retryTarget":"destDB","retryTime":297,"retrying":true}

DTS-RETRY-ERR-0043: MySQL binlog (.*)? is not exists

Possible cause: The task is paused for more than seven days, or the retention period of MySQL binary logs is short. As a result, binary logs do not exist.

dts-k-src: DTS-52110: MySQLRecordExtractor Init Error: mysql-reader: DTS-52212: MySQL binlog 1664283982 is not exists.

DTS-RETRY-ERR-0044: Get Last Position Error

Possible cause: An error occurs when DTS queries the global transaction identifier (GTID) of a transaction.

Solution: Contact Alibaba Cloud technical support.

id=34293****, jobId=vheu6zm1297****, value={"errMsg":"dts-k-src: DTS-52121: Get Last Position Error.","jobId":"p83i1t3912i****","maxRetryTime":7200,"module":"reader","retryCount":30,"retryTarget":"dstore","retryTime":2911,"retrying":true}

DTS-RETRY-ERR-0045: archiver error (.*)? Connect internal only (.*)? until freed

Possible cause: The space for the archived log files of the Oracle database is full, or the space of the root directory is full. As a result, an archive task cannot run.

Solution: Check whether the space for the archived log files of the Oracle database is full, or whether the space of the root directory is full.

id=34291****, jobId=zl0110ae27t****, value={"errMsg":"ORA-00257: archiver error. Connect internal only, until freed.\n@error code:257","jobId":"o50118un27m****","maxRetryTime":43200,"module":"reader","retryCount":90,"retryTarget":"srcDB","retryTime":903,"retrying":true}

DTS-RETRY-ERR-0046: Access denied for user

Possible cause 1: The database account that is used by the DTS task does not have the required permissions.

Possible cause 2: The database mentioned in the error message is a system database, such as the sys database, or a database that does not need to be synchronized or migrated.

id=34298****, jobId=c7e10qex28q****, value={"errMsg":"dts-k-src: DTS-52110: MySQLRecordExtractor Init Error: mysql-reader: DTS--0002: MySQLMessageNotifier notifyConnectionException error Access denied for user 'edy_dba1'@'10.28.XX.XX' (using password: YES)","jobId":"k361016128e****","maxRetryTime":7200,"module":"reader","retryCount":18,"retryTarget":"srcDB","retryTime":730,"retrying":true}

DTS-RETRY-ERR-0047: The MySQL server is running with the --read-only option

Possible cause: The MySQL instance is a read-only instance.

Solution: Modify the configurations of the MySQL instance. For more information, see Strange MySQL "read-only" error.

id=34297****, jobId=d3a107cy29z****, value={"errMsg":"framework: DTS-30011: currentRunningSQL: /* DTS-full-g86108c2294**** */insert ignore into `mpm_workflow`.`tb_node_tasks`(`tenant_id`,`task_name`,`reviewer_node_rp_info`,`node_status`,`create_time`,`punish_b_mp`,`last_node_info`,`approval_type`,`end_time`,`task_id`,`read_flag`,`is_last_flag`,`reward_b_mp`,`proc_inst_id`,`id`,`assignee`,`last_mod_time`,`reviewer_reward_b_mp`) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?), reason: The MySQL server is running with the --read-only option so it cannot execute this statement\ncause:\n\tBatchUpdateException: The MySQL server is running with the --read-only option so it cannot execute this statement\n\tSQLException: The MySQL server is running with the --read-only option so it cannot execute this statement","jobId":"g86108c2294****","maxRetryTime":7200,"module":"full","retryCount":175,"retryTarget":"destDB","retryTime":6149,"retrying":true}

DTS-RETRY-ERR-0048: object mapping for (.*)? tried to parse field (.*)? as object (.*)? but found a concrete value

Possible cause: Schema migration or synchronization is not selected for the DTS task and field type mapping fails.

Solution: Modify the schema of the destination table so that mapping can be performed for the fields mentioned in the error message. For more information, see Tried to parse field as object, but found a concrete value.

id=34298****, jobId=o0g115h4l19****, value={"errMsg":"common: DTS-11005: es: DTS-10035: object mapping for [ext_info.storeSnapshot] tried to parse field [storeSnapshot] as object, but found a concrete value\ncause:\n\tIOException: es: DTS-10035: object mapping for [ext_info.storeSnapshot] tried to parse field [storeSnapshot] as object, but found a concrete value\n\tCriticalAnyAllException: es: DTS-10035: object mapping for [ext_info.storeSnapshot] tried to parse field [storeSnapshot] as object, but found a concrete value","jobId":"k5d111rgn1q****","maxRetryTime":7200,"module":"full","retryCount":8,"retryTarget":"destDB","retryTime":188,"retrying":true}

DTS-RETRY-ERR-0049: get table (.*)? detail info failed (.*)? No operations allowed after connection closed

Possible cause: You modify the name of the destination database when the task is running. As a result, DTS fails to connect to the destination database.

Solution: Check whether the database exists and make sure that the database can be connected.

id=34443****, jobId=vnie8qsym6j****, value={"errMsg":"replicate-adb30: DTS-70002: get table [center_item.t_ite_half_product_list] detail info failed.\ncause:\n\tMySQLNonTransientConnectionException: No operations allowed after connection closed.","jobId":"xlcu9y7a29s****","maxRetryTime":43200,"module":"writer","retryCount":42,"retryTarget":"destDB","retryTime":415,"retrying":true}

DTS-RETRY-ERR-0050: get table (.*)? detail info failed (.*)? Schema (.*)? does not exist

Possible cause: The schema does not exist because the name of the destination database is modified.

Solution: Check whether the schema exists.

id=34443****, jobId=vnie8qsym6j****, value={"errMsg":"replicate-adb30: DTS-70002: get table [center_item.t_ite_sale_product_list] detail info failed.\ncause:\n\tSQLException: [20019, 2022110223221517201625218803151866591] : Schema center_item does not exist","jobId":"xlcu9y7a29s****","maxRetryTime":43200,"module":"writer","retryCount":13,"retryTarget":"destDB","retryTime":128,"retrying":true}

DTS-RETRY-ERR-0051: execute statement failed (.*)? The MySQL server is running with the LOCK_WRITE option

Possible cause: DTS cannot write data because an exception occurs on the MySQL instance. For example, the MySQL instance is in the LOCK_WRITE state.

Solution: Check the status of the MySQL instance.

id=34443****, jobId=v2310b2h13d****, value={"errMsg":"transaction-replicate: DTS-70003: 29 execute transaction has excess max transaction retry time [150] cause:transaction-replicate: DTS-70004: execute statement failed, may try it again\ncause:\n\tRecoverableAnyAllException: transaction-replicate: DTS-70004: execute statement failed, may try it again\n\tSQLException: MysqlEngine(29): meet error, insertSQL:/* DTS-writer-pt0104ov13b****-MysqlEngine(29) */insert into `gts`.`s1` (`address`,`gender`,`name`,`telephone`,`id`,`department`,`age`)  VALUES  (x'E6B19FE88B8FE79C81E58D97E4BAACE5B882E696B0E59F8EE7A791E68A80E59BAD', x'E794B7', x'E5AE8BE6B19F', x'3133383031323334353637', 80371, x'416C6979756E', 28) , error detail message:The MySQL server is running with the LOCK_WRITE option so it cannot execute this statement\n\tSQLException: The MySQL server is running with the LOCK_WRITE option so it cannot execute this statement","jobId":"pt0104ov13b****","maxRetryTime":86400,"module":"writer","retryCount":372,"retryTarget":"destDB","retryTime":10201,"retrying":true}

DTS-RETRY-ERR-0052: Record Replicator error in table (.*)? The table (.*)? does not have primary key!

Possible cause: A table in the destination database does not have a primary key.

Solution: Define a primary key for the table in the destination database based on the primary key settings of the corresponding table in the source database. Then, restart the task.

DTS-077100: Record Replicator error in table null.null. cause by [The table `reader`.`my_table` does not 
have primary key!] About more information in [https://**.ali**.com/**].

DTS-RETRY-ERR-0053: Failed to get offsets by times in 120000 ms

Possible cause: The incremental write module cannot connect to the incremental data collection module due to network jitters.

Solution: Restart the incremental write module and check whether the task can be resumed.

org.apache.kafka.common.errors.TimeoutException: Failed to get offsets by times in 120000 ms

DTS-RETRY-ERR-0054: Failed to get offsets by times in 60000 ms

Possible cause: The incremental data collection module cannot connect to the data cache module due to network jitters.

Solution: Restart the incremental data collection module and check whether the task can be resumed.

Failed to get offsets by times in 60000 ms

DTS-RETRY-ERR-0055: In process of processing data (.*)? failed (.*)? column (.*)? does not exist

Possible cause: A column is not found in the destination table.

Solution: Add the missing column to the destination table and restart the task.

In process of processing data (recordRange: 767384901729753****) failed
cause:
    CriticalAnyAllException: framework: DTS-30020: execute sql:/* DTS-full-t6o10oly31f**** */SELECT a,b FROM default$default."_AnswerDetailToSectionScore" --> (null, null) record range id = 767384901729753****, fetchSize = 1024
    PSQLException: ERROR: column "a" does not exist

DTS-RETRY-ERR-0056: In process of processing data (.*)? failed (.*)? read source data error (.*)? An I/O error occurred while sending to the backend

Possible cause: The destination database has heavy loads or the network is unstable.

In process of processing data (recordRange: 361479547447882****) failed
cause:
    CriticalAnyAllException: framework: DTS-31009: read source data error
    PSQLException: An I/O error occurred while sending to the backend.

DTS-RETRY-ERR-0057: fetch column info from target table (.*)? failed (.*)? Can not get the column

Possible cause 1: A full data migration task of DTS cannot migrate a global index.

Solution: Delete the global index from the destination database.

Possible cause 2: DTS does not support the MyISAM storage engine that is used by the database.

framework: DTS-31008: fetch column info from target table snpcenter.modification failed
cause:
    AnyCoreException: framework: DTS-31008: fetch column info from target table snpcenter.modification failed
    CriticalAnyAllException: full-postgresql: DTS-61008: jdbc: DTS-11014: Can not get the column tableoid from recordSchema for index global_modification_after_idx

DTS-RETRY-ERR-0058: fetch column info from (.*)? table (.*)? failed (.*)? relation (.*)? does not exist

Possible cause 1: The specified table does not exist in the destination database.

Solution: Create the table in the destination database. If you need to delete the table from the destination database, delete the table after the task is complete.

Possible cause 2: DTS does not support the MyISAM storage engine that is used by the database.

framework: DTS-31008: fetch column info from source table dw.tmp_smb2021 failed
cause:
    AnyCoreException: framework: DTS-31008: fetch column info from source table dw.tmp_smb2021 failed
    CriticalAnyAllException: full-postgresql: DTS-61008: ERROR: relation "dw.tmp_smb2021" does not exist

DTS-RETRY-ERR-0059: fetch column info from (.*)? table (.*)? failed (.*)? NullPointerException

Possible cause 1: DTS fails to query the schema information of the specified table in the source database. The table may have been deleted from the source database, or the configured account of the source database does not have the query permissions on the table.

Solution: Check whether the table exists in the source database. If the table is deleted, reconfigure the DTS task. If the table exists, check whether the configured account of the source database has the query permissions on the table. If the account does not have the query permissions on the table, grant the permissions to the account.

Possible cause 2: DTS does not support the MyISAM storage engine that is used by the database.

**
cause:
    AnyCoreException: framework: DTS-31008: fetch column info from source table xxx.yyy failed
    NullPointerException: null

DTS-RETRY-ERR-0060: Table (.*)? doesn't exist

Possible cause: The specified table does not exist in the destination database.

Solution: Create the table in the destination database. If you need to delete the table from the destination database, delete the table after the task is complete.

    cause:
    BatchUpdateException: Table 'hd_new_cctv.tbl_program' doesn't exist
    MySQLSyntaxErrorException: Table 'hd_new_cctv.tbl_program' doesn't exist"

DTS-RETRY-ERR-0061: Duplicate entry (.*)? for key

Possible cause: A primary key conflict occurs when DTS writes data to the destination database. A trigger may exist in the destination database. When DTS writes data to the database, this trigger is fired and a primary key conflict is triggered.

Solution: View the database and table information in the SQL statement that fails, check whether a trigger exists in the destination database, and then evaluate whether the trigger can be deleted. After the trigger is deleted, restart the DTS task.

Duplicate entry '97103673' for key 'PRIMARY'
cause:
    BatchUpdateException: Duplicate entry '9710****' for key 'PRIMARY'
    MySQLIntegrityConstraintViolationException: Duplicate entry '9710****' for key 'PRIMARY'"

DTS-RETRY-ERR-0062: column (.*)? of relation (.*)? does not exist

Possible cause: The schemas of tables in the source and destination databases are inconsistent. A column does not exist in the specified table of the destination database.

Solution: Add the missing column to the specified table of the destination database and restart the task.

ERROR: column "exception" of relation "t_m_class_record_detail" does not exist

DTS-RETRY-ERR-0063: Lock wait timeout exceeded

Possible cause: A lock wait timeout occurs in the destination database.

SHOW FULL PROCESSLIST;
SELECT * FROM innodb_trx;

reason: Lock wait timeout exceeded; try restarting transaction
cause:
    BatchUpdateException: Lock wait timeout exceeded; try restarting transaction
    MySQLTransactionRollbackException: Lock wait timeout exceeded; try restarting transaction

DTS-RETRY-ERR-0064: schema in dblist not found in database

Possible cause: A specific schema does not exist in the destination database.

Solution: Create the schema and tables to be migrated in the schema in the destination database. Then, restart the task.

schema in dblist not found in database

DTS-RETRY-ERR-0065: syntax error at or near (.*)? schema (.*)? does not exist

Possible cause: A specific schema does not exist in the destination database.

Solution: Create the schema and tables to be migrated in the schema in the destination database. Then, restart the task.

Example:

ERROR:syntax error at or near \"\"ALTER\"\"
Position:157. ERROR: schema \"\"CECDEV\"\" does not exist.

DTS-RETRY-ERR-0066: MongoCommandException (.*)? Command failed with error (.*)? requires authentication

Possible cause: The account of the destination database does not have the write permissions.

Solution: Grant the write permissions to the destination database account.

MongoCommandException:
Command failed with error 13: 'command insert requires authentication' on
server 113.**.*.*:27017. 

DTS-RETRY-ERR-0067: MongoCommandException (.*)? Command failed with error (.*)? disk locked

Possible cause: The disk of the destination database is locked. The disk space may be full.

Solution: Increase the disk space for the destination MongoDB database and restart the task.

MongoCommandException:
Command failed with error 13: 'cloud instance error, disk locked, plz check and
upgrade your disk quota, extra info: not authorized on gankao_log to execute
command { insert: "jyquestions", ordered: true, bypassDocumentValidation:
true, $db: "gankao_log" }' on server 100.**.*.*:27017.

DTS-RETRY-ERR-0068: invalid set null value to not nullable field

Possible cause: The source and destination databases have inconsistent schemas. A field in the source database is NULLABLE, whereas the corresponding field in the destination database is NOT NULL.

Solution: Find the table in the destination database based on the error message, change the type of the field in the table to NULLABLE, and then restart the task.

CriticalAnyAllException: database-commons: DTS-11001: invalid set null value to not nullable field

DTS-RETRY-ERR-0069: Datasource rejected establishment of connection (.*)? Too many connections

Possible cause: The number of connections to the source or destination database has reached the upper limit.

MySQLNonTransientConnectionException: Data source rejected establishment of connection,  message from server: ""Too many connections"""

DTS-RETRY-ERR-0070: In process of processing data (.*)? failed (.*)? Syntax error in SQL statement

Possible cause: The fields used to filter the objects to be synchronized are specified in an invalid format.

Solution: Modify the filter conditions of the objects to be synchronized by removing the WHERE keyword. Then, restart the task.

framework: DTS-31009: In process of processing data (recordRange:
631*****493978*****) failed cause:
CriticalAnyAllException: common: DTS-11005: Syntax error in SQL statement
"WHERE[*] UPDATED_TIME > '2022-11-02' " [42000-193] 

DTS-RETRY-ERR-0071: In process of processing data (.*)? failed (.*)? Fetch records (.*)? times but return empty

Possible cause: The incremental write module cannot obtain data from the incremental data collection module.

Solution: Troubleshoot the error returned from the incremental data collection module.

\"framework: DTS-31009: In process of processing data (recordRange: 651*****493978*****) failed\n" +
                "cause:\n" +
                "\tCriticalAnyAllException: common: DTS-10009: capture-dstore: DTS-51009: Fetch records 156 times but return empty.\n" +
                "\tRecoverableAnyAllException: capture-dstore: DTS-51009: Fetch records 156 times but return empty.\n" +
                "\tException: Fetch records but return empty.\"

DTS-RETRY-ERR-0072: In process of processing data (.*)? failed (.*)? Failed to get offsets by times in 120000 ms

Possible cause: The incremental write module cannot obtain data from the incremental data collection module.

Solution: Restart the incremental write module and check whether the task can be resumed.

\"framework: DTS-31009: In process of processing data (recordRange: 3187189853338992640) failed\n" +
                "cause:\n" +
                "\tCriticalAnyAllException: common: DTS-11005: Failed to get offsets by times in 120000 ms\n" +
                "\tTimeoutException: Failed to get offsets by times in 120000 ms\"

DTS-RETRY-ERR-0073: In process of processing data (.*)? failed (.*)? unreachable source redis network

Possible cause: DTS cannot connect to the Redis instance, or the Redis instance may be released.

Solution: Check whether the Redis instance can be connected.

\"framework: DTS-31009: In process of processing data (recordRange: 278730492608512) failed\n" +
                "cause:\n" +
                "\tRedisServerException: redis: DTS-10015: unreachable source redis network.\n" +
                "\tSocketException: Broken pipe (Write failed)\"

DTS-RETRY-ERR-0074: JedisDataException (.*)? WRONGTYPE Operation against a key holding the wrong kind of value

Possible cause: A specific key in the destination database shares the same name as a key in the source database. However, the two keys are of different types.

Solution: Delete the key with the same name from the destination database.

redis.clients.jedis.exceptions.JedisDataException: WRONGTYPE Operation against a key holding the wrong kind of value

DTS-RETRY-ERR-0075: sqlserver-reader (.*)? seek binlog for timestamp

Possible cause: No logs are generated at the corresponding point in time in the source database.

Solution: Reconfigure the task.

"\tCriticalAnyAllException: sqlserver-reader: DTS-52061: Failed to
seek sqlserver position\n" +

DTS-RETRY-ERR-0076: SQLServerException (.*)? The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer

Possible cause: The database cannot be connected.

Solution: Make sure that the database can be connected and restart the task. If the error persists, contact Alibaba Cloud technical support.

"cause:\n" +
     "\tSQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: \"\"Unexpected rethrowing\"\".\n" +

DTS-RETRY-ERR-0077: Increment Context Is Not Running (.*)? please check whether binlog_row_image=FULL

Possible cause: The binary logging mode is invalid. DTS can read the binary logs of a MySQL database only if the binlog_row_image parameter is set to FULL.

\"dts-k-src:
DTS-52111: Increment Context Is Not Running..: \n" +
 "cause:\n" +
"\tCriticalAnyAllException: mysql-reader: DTS-52210: fetch log
failed\n" +
"\tIOException: java.lang.UnsupportedOperationException:
database:palm_all/table:p_player/charSet:utf8/rdsRowid:false/filter:false/engine:InnoDB/snapshot:16659793***** Null bitmap size check error, binlog
table map has 15 columns, but row event has {0}, please check whether
binlog_row_image=FULL and binlog event Header:

DTS-RETRY-ERR-0078: Fetch records (.*)? times but return empty

Possible cause: The incremental write module cannot obtain data from the incremental data collection module.

Solution: Troubleshoot the error returned from the incremental data collection module and restart the task. If the error persists, contact Alibaba Cloud technical support.

\"framework: DTS-31009: In process of processing data
(recordRange: 65147****8075******) failed\n" +
"cause:\n" +
    "\tCriticalAnyAllException: common: DTS-10009: capture-dstore:
    DTS-51009: Fetch records 156 times but return empty.\n" +

DTS-RETRY-ERR-0079: execute statement failed (.*)? MySQLSyntaxErrorException

Possible cause: The destination database does not support the SQL statement mentioned in the error message.

Solution: Contact Alibaba Cloud technical support.

id=34439****, jobId=z48c4r42s8c****, value={"errMsg":"transaction-replicate: DTS-70004: execute statement failed: /*dts_id=dtsrrrm4ar8v83z6vk*/alter table `xp_ass`.`t_se_db_shop_wi_coef` ADD \ncause:\n\tMySQLSyntaxErrorException: [13000, 2022110222143119216819915303151843457] illegal name, pos 47, line 1, column 48, token EOF","jobId":"hbsk4mjdr83****","maxRetryTime":7200,"module":"writer","retryCount":3,"retryTarget":"destDB","retryTime":4399,"retrying":true}

DTS-RETRY-ERR-0080: Disperse target record field (.*)? unsupported value convert

Possible cause: DTS cannot perform type conversion because the schemas of tables in the source and destination databases are inconsistent.

Solution: Modify the schema of the table in the destination database to be the same as that in the source database. Then, restart the task.

id=34436****, jobId=wm811y74h1q****, value={"errMsg":"transaction-framework: DTS-71001: Disperse target record field updatetime STRING nullable as updatetime failed for record LazyParseRecord {offset [726070057], operationType [INSERT], checkpoint [0@726070057@102578064@1807@1667391476000]}\ncause:\n\tJdbcUtilsException: jdbc-utils: DTS-11001: MysqlTimestampValueDisperse: unsupported value convert for [2022-11-02 20:17:56.0] convert to [updatetime STRING nullable as updatetime]","jobId":"o7x11euhn1d****","maxRetryTime":7200,"module":"writer","retryCount":55,"retryTarget":"destDB","retryTime":546,"retrying":true}

DTS-RETRY-ERR-0081: WSREP has not yet prepared node for application use

Possible cause: An exception occurs on the database.

Solution: Troubleshoot the error in the database and restart the DTS instance.

id=34436****, jobId=s7i127j4225****, value={"errMsg":"WSREP has not yet prepared node for application use@error code:
1047","jobId":"frjr8yzg17z****","maxRetryTime":43200,"module":"reader","retryCount":1503,"retryTarget":"srcDB","
retryTime":15155,"retrying":true}

DTS-RETRY-ERR-0082: Failed to disperse record LazyParseRecord

Possible cause: An error occurs when DTS generates an SQL statement.

Solution: Make sure that the schemas of tables in the source and destination databases are consistent or compatible, and restart the task. For a data synchronization task, you can remove the table mentioned in the error message from the objects to be synchronized and restart the task. For more information, see Remove an object from a data synchronization task.

id=34441****, jobId=tidd773a278****, value={"errMsg":"transaction-framework: DTS-71001: Failed to disperse record LazyParseRecord {offset [1311857846], operationType [UPDATE], checkpoint [0@1311857846@17610008188031@1667388377000]} in buildWhereClause.\ncause:\n\tTransactionReplicateException: transaction-replicate: DTS-71001: MysqlRelatedTextSqlBuilderTools: record [LazyParseRecord ****

DTS-RETRY-ERR-0083: Error while executing user ETL (.*)? not found in

Possible cause: The ETL syntax is invalid. As a result, the ETL task fails.

Solution: Check whether the ETL syntax is valid based on the error message.

id=34441****, jobId=p4d110p0o25****, value={"errMsg":"ETL: DTS--0001: Error while executing user ETL: starttime not found in cco_consult_platform_0002.web_chat_session_0263\ncause:\n\tRuntimeException: starttime not found in cco_consult_platform_0002.web_chat_session_0263","jobId":"ed611zroy2m****","maxRetryTime":7200,"module":"full","retryCount":14,"retryTarget":"srcDB","retryTime":135,"retrying":true}

DTS-RETRY-ERR-0084: User (.*)? does not have (.*)? privilege on

Possible cause: The database account that is configured for the task does not have the required permissions.

Solution: Grant the required permissions to the database account that is used by the DTS task based on the error message.

id=34441****, jobId=r5g11018w2m****, value={"errMsg":"[1528a0144000****][11.202.XX.XX:3053][polardbx]ERR-CODE: [TDDL-5108][ERR_CHECK_PRIVILEGE_FAILED_ON_TABLE] User test@'100.104.XX.XX' does not have 'REPLICATION_CLIENT' privilege on table 'person'. Database is *. @error code:5108","jobId":"fr611dvxq2d****","maxRetryTime":7200,"module":"reader","retryCount":24,"retryTarget":"srcDB","retryTime":220,"retrying":true}

DTS-RETRY-ERR-0085: execute statement failed (.*)? modify decimal column is disabled

Possible cause: DDL operations for modifying columns are not allowed on the destination table.

id=34445****, jobId=qa1u5qhp276****, value={"errMsg":"transaction-replicate: DTS-70004: execute statement failed: /*dts_id=dtsqa1u5qhp276p****/alter table `ectouch_data`.`order_v0_data` modify column `ka_commission_rate` DECIMAL(11, 4) default 0.00 comment 'ka**'\ncause:\n\tSQLException: [15018, 202211030027061921681310090345394****] modify decimal column is disabled, col=ka_commission_rate, oldType=decimal(11,2), newType=decimal(11,4)","jobId":"nd7k53au27e****","maxRetryTime":43200,"module":"writer","retryCount":3104,"retryTarget":"destDB","retryTime":31341,"retrying":true}

DTS-RETRY-ERR-0086: Query execution was interrupted (.*)? max_statement_time exceeded

Possible cause: The execution of an SQL query statement has timed out.

Solution: Run the set max_statement_time=0 command to set the execution of SQL statements to never time out and then restart the task.

id=34445****, jobId=v4kg7039n3m****, value={"errMsg":"Query execution was interrupted, max_statement_time exceeded@error code:3006","jobId":"wchy7vcw20m****","maxRetryTime":1800,"module":"reader","retryCount":2,"retryTarget":"srcDB","retryTime":3,"retrying":true}

DTS-RETRY-ERR-0087: execute statement failed (.*)? Cannot find the object

Possible cause 1: The object does not exist.

Solution: Check whether the object mentioned in the error message exists.

Possible cause 2: The database account that is used by the task does not have the required permissions.

Solution: Check whether the database account that is used by the task has the required permissions.

id=34447****, jobId=q7j108h020a****, value={"errMsg":"transaction-replicate: DTS-70004: execute statement failed: null\ncause:\n\tSQLServerException: Cannot find the object \"lhrdme-test-client-C01.dbo.send_document_task\" because it does not exist or you do not have permissions.","jobId":"q8i1043620d****","maxRetryTime":86400,"module":"writer","retryCount":163,"retryTarget":"destDB","retryTime":1636,"retrying":true}

DTS-RETRY-ERR-0088: can not find disperser for column

Possible cause: The columns in the destination table are incompatible with the columns in the source table.

id=34447****, jobId=tpe1121dl2f****, value={"errMsg":"database-framework: DTS-61001: can not find disperser for column:hold_court_time TIME_WITH_TIMEZONE nullable as hold_court_time of table:public.lms_lc_case valueType= value=null","jobId":"rj9113j7m28****","maxRetryTime":7200,"module":"full","retryCount":161,"retryTarget":"destDB","retryTime":1608,"retrying":true}

DTS-RETRY-ERR-0089: BatchUpdateException (.*)? Cannot insert explicit value for identity column

Possible cause: By default, data cannot be inserted into auto-increment fields in an SQL Server table.

Solution: Change the value of the IDENTITY_INSERT attribute of the table mentioned in the error message to ON and restart the task.

id=34453****, jobId=jn81159sr3m****, value={"errMsg":"common: DTS-11005: Cannot insert explicit value for identity column in table 'Card_Msyy' when IDENTITY_INSERT is set to OFF.\ncause:\n\tBatchUpdateException: Cannot insert explicit value for identity column in table 'Card_Msyy' when IDENTITY_INSERT is set to OFF.","jobId":"gl111n9sb33****","maxRetryTime":7200,"module":"full","retryCount":99,"retryTarget":"destDB","retryTime":2686,"retrying":true}

DTS-RETRY-ERR-0090: The query has timed out

Possible cause: Data is modified in the source database. As a result, data cannot be queried.

Solution: Wait for DTS to automatically retry.

id=34450****, jobId=lh9n33tj30o****, value={"errMsg":"The query has timed out.@error code:0","jobId":"b27g31tn30l****","maxRetryTime":43200,"module":"reader","retryCount":27,"retryTarget":"srcDB","retryTime":810,"retrying":true}

DTS-RETRY-ERR-0091: Transaction (.*)? was deadlocked on lock resources with another process

Possible cause: A deadlock occurs in the database transaction.

Solution: Contact Alibaba Cloud technical support.

id=34453****, jobId=jn81159sr3m****, value={"errMsg":"common: DTS-11005: Transaction (Process ID 187) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.\ncause:\n\tSQLServerException: Transaction (Process ID 187) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.","jobId":"gl111n9sb33****","maxRetryTime":7200,"module":"full","retryCount":1,"retryTarget":"destDB","retryTime":10,"retrying":true}

DTS-RETRY-ERR-0093: get table (.*)? detail info failed (.*)? relation (.*)? does not exist

Possible cause: The table mentioned in the error message does not exist.

Solution: Check whether the table mentioned in the error message exists in the source and destination databases. If the table does not exist in the destination database, manually create the table and restart the task.

id=34488****, jobId=z65o4ny9c1o****, value={"errMsg":"replicate-greenplum: DTS-70002: get table [schema=hobby_om, database=hobby_om, table=tp_3321167_ogl_sys_user] detail info failed.\ncause:\n\tPSQLException: ERROR: relation \"hobby_om.tp_3321167_ogl_sys_user\" does not exist\n  Position: 15","jobId":"jdag45haa17****","maxRetryTime":7200,"module":"writer","retryCount":62,"retryTarget":"destDB","retryTime":615,"retrying":true}

DTS-RETRY-ERR-0097: execute statement failed (.*)? unsupported delete without primary keys defined

Possible cause: The table to be synchronized or migrated does not have a primary key or UNIQUE constraint.

Solution: Add a primary key or UNIQUE constraint to the table to be synchronized or migrated, and restart the task.

id=34484****, jobId=l69119srl3n****, value={"errMsg":"transaction-replicate: DTS-70004: execute statement failed: /*dts_id=dtss6x11x32l3858ap*/delete from `zx`.`tb_abc` where `a` = 7 and `b` = 7 and `c` = 7 and `d` = 7\ncause:\n\tSQLException: ADB30Engine(1): meet error, deleteSQL:/*dts_id=dtss6x11x32l3858ap*/delete from `zx`.`tb_abc` where `a` = 7 and `b` = 7 and `c` = 7 and `d` = 7, error detail message:[15018, 2022110315214019216806122303453480359] table => zx.tb_abc unsupported delete without primary keys defined\n\tSQLException: [15018, 2022110315214019216806122303453480359] table => zx.tb_abc unsupported delete without primary keys defined","jobId":"zyu118d2u31****","maxRetryTime":7200,"module":"writer","retryCount":11,"retryTarget":"destDB","retryTime":101,"retrying":true}

DTS-RETRY-ERR-0098: get table (.*)? detail info failed (.*)? The specified topic does not exist

Possible cause: The DataHub topic does not exist.

Solution: Check whether the topic mentioned in the error message exists. If the topic does not exist, create the topic and restart the task. For more information about how to create a topic, see Manage topics.

id=34474****, jobId=oh811gu0n14****, value={"errMsg":"replicate-datahub: DTS-70002: get table [bobo_data.bill_record] detail info failed.\ncause:\n\tResourceNotFoundException: [httpStatus:404, requestId:20221103112918ae38dc0b7925****, errorCode:NoSuchTopic, errorMessage:The specified topic does not exist.]","jobId":"z3w1153fq1o****","maxRetryTime":7200,"module":"writer","retryCount":4,"retryTarget":"destDB","retryTime":30,"retrying":true}

DTS-RETRY-ERR-0099: execute statement failed (.*)? column (.*)? is not nullable

Possible cause: Null values are inserted into columns that have the NOT NULL constraint in the destination table.

Solution: Remove the NOT NULL constraint from the columns mentioned in the error message in the destination table and restart the task.

 id=34470****, jobId=db411ak8d33****, value={"errMsg":"transaction-replicate: DTS-70004: execute statement failed: /*dts_id=dtspfb11r2bq3qj*****/replace into `jlg`.`new_collect_wxprefe` (`upload_time`,`upload_id`,`robot_id`,`jlg_wx_id`,`name`,`link`,`pid`,`origin_id`,`worktype_id`,`id`) values (null, 0, 0, 54842, '****', '', -1, 0, '', 2309713)\ncause:\n\tSQLException: ADB30Engine(22): meet error, insertSQL:/*dts_id=dtspfb11r2bq3qj****/replace into `jlg`.`new_collect_wxprefe` (`upload_time`,`upload_id`,`robot_id`,`jlg_wx_id`,`name`,`link`,`pid`,`origin_id`,`worktype_id`,`id`) values (null, 0, 0, 54842, '****', '', -1, 0, '', 2309713), error detail message:[15018, 2022110310293219216812802603151898161] syntax error :column 'NEW_COLLECT_WXPREFE.UPLOAD_TIME' is not nullable, can not set null\n\tSQLException: [15018, 2022110310293219216812802603151898161] syntax error :column 'NEW_COLLECT_WXPREFE.UPLOAD_TIME' is not nullable, can not set null","jobId":"ozn11934r3e****","maxRetryTime":7200,"module":"writer","retryCount":58,"retryTarget":"destDB","retryTime":573,"retrying":true}

DTS-RETRY-ERR-0100: execute statement failed (.*)? rename table (.*)? target table (.*)? already exists

Possible cause: The name that you want to specify for a table by using the RENAME operation already exists. As a result, the RENAME operation cannot be performed.

Solution: Check whether the table with the same name mentioned in the error message can be deleted. If the table can be deleted, delete the table and restart the task.

id=34497****, jobId=q3d10wi911k****, value={"errMsg":"transaction-replicate: DTS-70004: execute statement failed: /*dts_id=dtswg2p8k1ve9ko****/rename table `sdinfo`.`sd_manager_group` to `sdinfo`.`sd_manager_grop_1103`\ncause:\n\tSQLException: [15018, 2022110321094219216822816803453937381] target table sdinfo.sd_manager_grop_1103 already exists","jobId":"e9u10c7k11y****","maxRetryTime":1800,"module":"writer","retryCount":179,"retryTarget":"destDB","retryTime":1972,"retrying":true}

DTS-RETRY-ERR-0101: execute statement failed (.*)? The MySQL server is running with the LOCK_WRITE_GROWTH option

Possible cause: The disk space of the destination database is insufficient.

Solution: Extend the disk for the destination database and restart the task.

id=34490****, jobId=woqu1l38176****, value={"errMsg":"transaction-replicate: DTS-70003: 22 execute transaction has excess max transaction retry time [150] cause:transaction-replicate: DTS-70004: execute statement failed, may try it again\ncause:\n\tRecoverableAnyAllException: transaction-replicate: DTS-70004: execute statement failed, may try it again\n\tSQLException: MysqlEngine(22): meet error, insertSQL:/* DTS-writer-vwqv11b6176****-MysqlEngine(22) */insert into `bi`.`b_resource_usage` (`created_time`,`updated_time`,`user_id`,`usage`,`resource_id`,`id`,`collect_day`,`accounting_day`)  VALUES  ('2022-02-12 06:00:00.0', '2022-02-12 06:00:00.0', x'53454C462D386F7855365F7173756452663438434B556A4B3351727A506A5873325135694B31674B79787674622D5041', 0, 4, 40386002, '2022-02-12', '2022-02-11') , error detail message:The MySQL server is running with the LOCK_WRITE_GROWTH option so it cannot execute this statement\n\tSQLException: The MySQL server is running with the LOCK_WRITE_GROWTH option so it cannot execute this statement","jobId":"vwqv11b6176****","maxRetryTime":43200,"module":"writer","retryCount":215,"retryTarget":"destDB","retryTime":4892,"retrying":true}

DTS-RETRY-ERR-0102: execute statement failed (.*)? IDENTITY_INSERT is already ON for table

Possible cause: You can set the IDENTITY_INSERT attribute to ON for only one table in a DTS instance. A table whose IDENTITY_INSERT attribute is set to ON already exists in the DTS instance.

Solution: Set the sink.batch.enable parameter to false for the DTS instance and restart the task. For more information, see Modify the parameters of a DTS instance.

id=34493****, jobId=jn81159sr3m****, value={"errMsg":"transaction-replicate: DTS-70004: execute statement failed: /*euy110qoz3vv6ywSQLServerPrepareStatementSqlEngine(30)*/delete top(1) from [HTOLMain].[dbo].[Cl_Order] where [OrderID] = ?\ncause:\n\tSQLServerException: IDENTITY_INSERT is already ON for table 'HTOLMain.dbo.Cl_Order'. Cannot perform SET operation for table 'HTOLMain.dbo.Cl_OrderItem'.","jobId":"euy110qoz3v****","maxRetryTime":7200,"module":"writer","retryCount":143,"retryTarget":"destDB","retryTime":1429,"retrying":true}

DTS-RETRY-ERR-0103: execute statement failed (.*)? column (.*)? of relation (.*)? does not exist

Possible cause: A column does not exist in the destination table.

Solution: Add the missing column to the specified table of the destination database based on the schema of the table in the source database and error message. Then, restart the task.

id=34488****, jobId=a3y11921r1e****, value={"errMsg":"transaction-replicate: DTS-70004: execute statement failed: /*f3l11pceo1h85zi29*/insert into default$default.\"_QuestionTypesToQuestions\" (a,b) values(?, ?)\ncause:\n\tPSQLException: ERROR: column \"a\" of relation \"_QuestionTypesToQuestions\" does not exist\n  Position: 79","jobId":"f3l11pceo1h****","maxRetryTime":7200,"module":"writer","retryCount":143,"retryTarget":"destDB","retryTime":1436,"retrying":true}

DTS-RETRY-ERR-0104: The transaction log for database (.*)? is full

Possible cause: The storage space for transaction logs or the disk space of the database is full.

Solution: Increase the storage space for transaction logs or the disk space and then restart the task.

id=34523****, jobId=f9q11u7qs3w****, value={"errMsg":"common: DTS-11005: The transaction log for database 'HTOLMain' is full due to 'AVAILABILITY_REPLICA'.\ncause:\n\tSQLServerException: The transaction log for database 'HTOLMain' is full due to 'AVAILABILITY_REPLICA'.","jobId":"fg6119hpu3f****","maxRetryTime":7200,"module":"full","retryCount":10,"retryTarget":"destDB","retryTime":251,"retrying":true}

DTS-RETRY-ERR-0105: Could not allocate space for object

Possible cause: The disk space of the destination database is full.

Solution: Extend the disk for the destination database and restart the task.

id=34523****, jobId=f9q11u7qs3w****, value={"errMsg":"common: DTS-11005: Could not allocate space for object 'dbo.Cl_OrderItem'.'ix_orderitem_productId' in database 'HTOLMain' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.\ncause:\n\tSQLServerException: Could not allocate space for object 'dbo.Cl_OrderItem'.'ix_orderitem_productId' in database 'HTOLMain' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.","jobId":"fg6119hpu3f****","maxRetryTime":7200,"module":"full","retryCount":102,"retryTarget":"destDB","retryTime":2663,"retrying":true}

DTS-RETRY-ERR-0106: Failed to seek sqlserver position (.*)? Fetch backup log failed (.*)? seek binlog for timestamp

Possible cause: SQL Server cannot find logs based on the log sequence number (LSN) when the task is started.

DTS-RETRY-ERR-0107: Fetch (.*)? SQL Server backup log faild (.*)? fetch ls

Possible cause: SQL Server cannot find logs based on the LSN when the task is running.

DTS-RETRY-ERR-0108: Column (.*)? For input string

Possible cause: The data format of the field mentioned in the error message is invalid.

Solution: Modify the data format of the field mentioned in the error message in the destination database and restart the task.

**** (Column => PMS_GOODS.RETAIL_INV_BUFFER), For input string: "0.4300"
    SQLException: [15018, 2022110322280517202801611203151004951] (Column => PMS_GOODS.RETAIL_INV_BUFFER), For input string: "0.4300"

DTS-RETRY-ERR-0109: In process of processing data (.*)? failed (.*)? Column (.*)? not found

Possible cause: A column does not exist in the destination table.

Solution: Add the missing column to the specified table of the destination database based on the schema of the table in the source database and error message. Then, restart the task.

\"framework: DTS-31009: In process of processing data (recordRange: 627098562752151552) failed\n" +
                "cause:\n" +
                "\tCriticalAnyAllException: common: DTS-11005: Column \"\"1658159900711\"\" not found [42122-193]\n" +
                "\tDbException: Column \"\"1658159900711\"\" not found [42122-193]\n" +
                "\tJdbcSQLException: Column \"\"1658159900711\"\" not found [42122-193]\"

DTS-RETRY-ERR-0110: In process of processing data (.*)? failed (.*)? RedisServerException (.*)? Slave connection closed by source redis

Possible cause: The connection to the source database is closed.

jobId=fo710zuy27x****, code=04, errMsg=framework: DTS-31009: In process of processing data (recordRange: 278730492608512) failed
cause:
    RedisServerException: redis: DTS-10015: Slave connection closed by source redis, please read /var/log/messages and redis server logs to find which caused this error.The most probable reason is insufficient memory, storage or slave output buffer(config set client-output-buffer-limit 'slave X X X').
    RedisCannotRetryException: redis: DTS-10009: Read 1037 bytes , but only 374 already read.
    IOException: Read 1037 bytes , but only 374 already read.

DTS-RETRY-ERR-0111: execute statement failed (.*)? null value in column (.*)? violates not-null constraint

Possible cause: Invalid data is generated when the task is running.

Solution: Check whether the schemas of tables in the source and destination databases are consistent.

jobId=a5oe7ffq12v****, code=07, errMsg=transaction-replicate: DTS-70004: execute statement failed: /*a5oe7ffq12vy4*****/insert into "resico_ods"."crm_cooperated_zlb" ("id","customer_id","zlb_info","remark","delete_flag","created_by","created_at","updated_by","updated_at","version","entp_name") values(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
cause:
    PSQLException: ERROR: null value in column "customer_id" violates not-null constraint  (seg3 172.26.254.254:4001 pid=308567)
  Detail: Failing row contains (158738364208513****, null, {"authAt":"2022-11-01 17:58:38","customerId":"15611694496311****..., null, 0, 0, 2022-11-01 17:58:47, 0, 2022-11-01 17:58:47+08, 0, ****).

DTS-RETRY-ERR-0112: execute statement failed (.*)? null value in column (.*)? For input string

Possible cause: Invalid data is generated when the task is running.

Solution: Check whether the schemas of tables in the source and destination databases are consistent.

jobId=jg910k6427x****, code=07, errMsg=transaction-replicate: DTS-70004: execute statement failed: /*dts_id=dtsb5r10cq5265*****/replace into `kuaishou_ad_dev`.`rel_ks_creative_master_account` (`master_id`,`account_id`,`updated_at`,`created_at`,`id`,`deleted_at`) values (3, 9999999999999, '2022-10-31 17:53:46.0', '2022-10-31 17:53:46.0', 28, null)
cause:
    SQLException: ADB30Engine(25): meet error, insertSQL:/*dts_id=dtsb5r10cq5265*****/replace into `kuaishou_ad_dev`.`rel_ks_creative_master_account` (`master_id`,`account_id`,`updated_at`,`created_at`,`id`,`deleted_at`) values (3, 9999999999999, '2022-10-31 17:53:46.0', '2022-10-31 17:53:46.0', 28, null), error detail message:[15018, 2022110118193219216818212703151020339] (Column => REL_KS_CREATIVE_MASTER_ACCOUNT.ACCOUNT_ID), For input string: "9999999999999"
    SQLException: [15018, 2022110118193219216818212703151020339] (Column => REL_KS_CREATIVE_MASTER_ACCOUNT.ACCOUNT_ID), For input string: "9999999999999"

DTS-RETRY-ERR-0113: table not exist

Possible cause: The table mentioned in the error message does not exist in the destination database.

SQLException: ADB30Engine(2): meet error, insertSQL:/*dts_id=dtsd4f12w00f8t*****/replace into `test_lianxi`.`ltkanduoduo1_full_att_realtime_std_hourly_report_v1` (`date`,`adgroup_id`,`hijack_agent_account_id`,`lowage_tuid_num`,`created_at`,`is_hijack`,`member_order_num`,`active_1day`,`hour`,`updated_at`,`last_week_active`,`id`,`campaign_id`,`create_role_num`,`url_report_num`,`dtu`,`os`,`cp_report_num`,`active`,`consumption`,`start_play_num`,`app_register_num`,`agent_account_id`,`ad_id`,`new_user_pass_num`,`login_num`,`key_action_num`,`yesterday_active`,`consumption_real`) values ('2022-11-01', 'att_4900014', 6, 0, '2022-11-01 17:00:07', 0, 0, 1, 17, '2022-11-01 17:15:16', 0, 146183, 'att_4900014', 0, 0, '4900014', 0, 0, 0, 0.00, 0, 0, 6, 'att_4900014', 0, 0, 0, 0, 0.00)error detail message:[15018, 2022110117151619216817607303151114839] table not exist => test_lianxi.ltkanduoduo1_full_att_realtime_std_hourly_report_v1
    SQLException: [15018, 2022110117151619216817607303151114839] table not exist => test_lianxi.ltkanduoduo1_full_att_realtime_std_hourly_report_v1

DTS-RETRY-ERR-0114: execute statement failed (.*)? Unknown column (.*)? in

Possible cause: A column does not exist in the specified table of the destination database.

Solution: Add the missing column to the specified table of the destination database and restart the task.

jobId=vme10ye5l8x****, code=07, errMsg=transaction-replicate: DTS-70004: execute statement failed: /* DTS-writer-vme10ye5l8xjbx7-MysqlEngine(29) */delete from `alt_coupon`.`report_coupon_order_statistics` WHERE `date` = '2022-10-31' and `ordamount` = 166050 and `usemem` = 45 and `expirecon` = 29573 and `allcon` = 21180 and `ordmem` = 45 and `coupon_name` = x'E887AAE58AA9E782B9E9A490E5858DE9858DE588B8' and `payamount` = 143550 and `usecon` = 45 and `__#alibaba_rds_row_id#__` = 14030 and `coupon_id` = 60 and `allmem` = 8470 and `ordcon` = 45 limit 1
cause:
    SQLException: MysqlEngine(29): meet error, deleteSQL:/* DTS-writer-vme10ye5l8xjbx7-MysqlEngine(29) */delete from `alt_coupon`.`report_coupon_order_statistics` WHERE `date` = '2022-10-31' and `ordamount` = 166050 and `usemem` = 45 and `expirecon` = 29573 and `allcon` = 21180 and `ordmem` = 45 and `coupon_name` = x'E887AAE58AA9E782B9E9A490E5858DE9858DE588B8' and `payamount` = 143550 and `usecon` = 45 and `__#alibaba_rds_row_id#__` = 14030 and `coupon_id` = 60 and `allmem` = 8470 and `ordcon` = 45 limit 1error detail message:Unknown column '__#alibaba_rds_row_id#__' in 'where clause'
    SQLSyntaxErrorException: Unknown column '__#alibaba_rds_row_id#__' in 'where clause'

DTS-RETRY-ERR-0123: The server principal (.*)? is not able to access the database (.*)? under the current security context

Possible cause: An error occurs when DTS queries metadata information.

Solution: Check whether the permissions of the database account that is used by the task meet relevant requirements and check whether the table mentioned in the error message exists in the source database.

\"common: DTS-11005: framework: DTS-31008: fetch column info from target table [U8CLOUD32CS].[dbo].[po_settlebill_b] failed\n" +
                "cause:\n" +
                "\tAnyCoreException: framework: DTS-31008: fetch column info from target table [U8CLOUD32CS].[dbo].[po_settlebill_b] failed\n" +
                "\tRuntimeException: com.microsoft.sqlserver.jdbc.SQLServerException: The server principal \"\"erp_user\"\" is not able to access the database \"\"U8CLOUD32CS\"\" under the current security context.\n" +
                "\tSQLServerException: The server principal \"\"erp_user\"\" is not able to access the database \"\"U8CLOUD32CS\"\" under the current security context.\"

DTS-RETRY-ERR-0124: Change data capture is only available in the Enterprise

Possible cause: The change data capture (CDC) feature is not supported by the SQL Server instance.

Solution: Check whether the SQL Server instance version allows you to enable CDC.

This instance of SQL Server is the Web Edition (64-bit). Change data capture is only available in the Enterprise, Developer, Enterprise Evaluation, and Standard editions.

DTS-RETRY-ERR-0125: MongoCommandException (.*)? interrupted at shutdown

Possible cause: An exception occurs on the MongoDB instance.

Solution: Check whether the MongoDB instance is running as expected.

\"common: DTS-11005: com.mongodb.MongoCommandException: Command failed with error 11600: 'interrupted at shutdown' on server 172.19.XX.XX:XXX. The full response is { \"\"ok\"\" : 0.0, \"\"errmsg\"\" : \"\"interrupted at shutdown\"\", \"\"code\"\" : 11600, \"\"codeName\"\" : \"\"InterruptedAtShutdown\"\" }\n" +
                "cause:\n" +
                "\tSQLException: com.mongodb.MongoCommandException: Command failed with error 11600: 'interrupted at shutdown' on server 172.19.XX.XX:XXX. The full response is { \"\"ok\"\" : 0.0, \"\"errmsg\"\" : \"\"interrupted at shutdown\"\", \"\"code\"\" : 11600, \"\"codeName\"\" : \"\"InterruptedAtShutdown\"\" }\n" +
                "\tMongoCommandException: Command failed with error 11600: 'interrupted at shutdown' on server 172.19.XX.XX:XXX. The full response is { \"\"ok\"\" : 0.0, \"\"errmsg\"\" : \"\"interrupted at shutdown\"\", \"\"code\"\" : 11600, \"\"codeName\"\" : \"\"InterruptedAtShutdown\"\" }\"

DTS-RETRY-ERR-0126: MongoCommandException (.*)? Index must have unique name

Possible cause: The index to be created already exists and cannot be created again.

Solution: Check whether an index with the same name exists. If an index with the same name exists and can be deleted, delete the index and restart the task.

com.mongodb.MongoCommandException: Command failed with error 86: 'Index must have unique name. The existing index: { v: 2, key: { fund_wallet_id: 1 }, name: "fund_wallet_id_1", ns: "airmart-watbg-prod.funds_pools", background: true } has the same name as the requested index: { v: 2, key: { fund_wallet_id: -1 }, name: "fund_wallet_id_1", ns: "airmart-watbg-prod.funds_pools", background: true }' on server 172.19.XX.XX:XXX. The full response is { "raw" : { "mgset-62336776/10.42.XX.XX:XXX,10.42.XX.XX:XXX" : { "ok" : 0.0, "errmsg" : "Index must have unique name.****

DTS-RETRY-ERR-0127: MongoCommandException (.*)? cloud instance error (.*)? disk locked

Possible cause: The disk of the MongoDB instance is locked. As a result, data cannot be written to the instance.

Solution: Check whether the disk space of the MongoDB instance is full. If the disk space is full, scale up the disk space of the instance and restart the task.

\"common: DTS-11005: com.mongodb.MongoCommandException: Command failed with error 13: 'cloud instance error, disk locked, plz check and upgrade your disk quota, extra info: not authorized on xmol to execute command { insert: \"\"thesisRedirectLogs\"\", ordered: true, bypassDocumentValidation: true, $db: \"\"xmol\"\" }' on server 172.16.19.23:42976. The full response is { \"\"operationTime\"\" : { \"\"$timestamp\"\" : { \"\"t\"\" : 1666348500, \"\"i\"\" : 3392 } }, \"\"ok\"\" : 0.0, \"\"errmsg\"\" : \"\"cloud instance error, disk locked, plz check and upgrade your disk quota, extra info: ****

DTS-RETRY-ERR-0128: Unknown database

Possible cause: The database does not exist.

Solution: Create the database mentioned in the error message and restart the task.

jobId=sw01037i31w****, code=04, errMsg=com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown database 'table3'

DTS-RETRY-ERR-0129: The table (.*)? is full

Possible cause 1: The disk space of the destination database is full.

jobId=zoa119hcy3m****, code=03, errMsg=framework: DTS-30011: currentRunningSQL: /* DTS-full-zoa119hcy3m**** */insert ignore into `statistics`.`t_mem_keyword_log`(`createtime`,`keyword_id`,`mem_id`,`ip`,`channel`,`id`,`source`,`TYPE`) VALUES (?,?,?,?,?,?,?,?), reason: The table 't_mem_keyword_log' is full
cause:
    BatchUpdateException: The table 't_mem_keyword_log' is full
    SQLException: The table 'DTSTEST' is full

Possible cause 2: The size of the temporary table has reached the upper limit.

You are using the MEMORY (HEAP) storage engine; in this case you need to increase the value of the max_heap_table_size system variable. See Section 5.1.3, "Server System Variables".
ERROR 1114 (HY000) at line 1720: The table 'XXXX' is full

DTS-RETRY-ERR-0130: BatchUpdateException (.*)? entry too large

Possible cause: The amount of written data exceeds the specified upper limit.

Solution: Set the value of the max_allowed_packet parameter to meet relevant requirements.

jobId=t7s100u5319****, code=03, errMsg=framework: DTS-30011: currentRunningSQL: /* DTS-full-t7s100u5319**** */insert ignore into `dcr_file_service`.`t_file_task`(`reason`,`company_id`,`create_time`,`entity_name`,`user_name`,`end_time`,`remark`,`sort`,`type`,`finish_time`,`enabled_flag`,`start_time`,`update_time`,`update_user`,`user_code`,`user_id`,`id`,`create_user`,`json_param`,`status`) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?), reason: entry too large, the max entry size is 6291456, the size of data is 7956719
cause:
    BatchUpdateException: entry too large, the max entry size is 6291456, the size of data is 7956719
    SQLException: entry too large, the max entry size is 6291456, the size of data is 7956719

DTS-RETRY-ERR-0131: BatchUpdateException (.*)? No space left on device

Possible cause: The disk space of DTS is full.

Solution: Contact Alibaba Cloud technical support.

jobId=wb611p3ef1h****, code=03, errMsg=framework: DTS-30011: currentRunningSQL: /* DTS-full-wb611p3ef1h**** */insert ignore into `dcs_ford_sale`.`tm_dcc_alloc_price_bak11`(`id`,`material_id`,`dealer_id`,`price_type`,`buy_type`,`origin`,`eff_date_from`,`eff_date_to`,`price`,`qty`,`qty_remain`,`status`,`psbi_create_date`,`create_date`,`update_date`,`ver`,`ver_date`,`update_by`,`src`,`sap_no`,`invoice_company`,`contract_no`,`xx_price_type`) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?), reason: Can't create/write to file '/tmp/MLHer8ya' (OS errno 28 - No space left on device)
cause:
    BatchUpdateException: Can't create/write to file '/tmp/MLHer8ya' (OS errno 28 - No space left on device)
    SQLException: Can't create/write to file '/tmp/MLHer8ya' (OS errno 28 - No space left on device)

DTS-RETRY-ERR-0133: fetch column info from target table (.*)? failed (.*)? Invalid object name

Possible cause: The table mentioned in the error message does not exist in the destination database.

Solution: Create a table in the destination database based on the error message and the information about the corresponding table in the source database. Then, restart the task.

jobId=sbl11ksji16****, code=03, errMsg=common: DTS-11005: framework: DTS-31008: fetch column info from target table [datang].[dbo].[SheBao_Source_1] failed
cause:
    AnyCoreException: framework: DTS-31008: fetch column info from target table [datang].[dbo].[SheBao_Source_1] failed
    RuntimeException: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'datang.dbo.SheBao_Source_1'.
    SQLServerException: Invalid object name 'datang.dbo.SheBao_Source_1'.

DTS-RETRY-ERR-0134: fetch column info from target table (.*)? failed

Possible cause 1: DTS fails to obtain the column information because columns are missing in the destination table.

Solution: Make sure that the corresponding columns exist in the destination table mentioned in the error message. Then, restart the task.

Possible cause 2: DTS fails to obtain the column information because the database account that is used by the DTS task does not have the required permissions.

Solution: Make sure that the database account that is used by the DTS task has the read and write permissions on the destination table. Then, restart the task.

Possible cause 3: The max_stack_depth parameter is set to a small value for the destination database.

Solution: Increase the value of the max_stack_depth parameter for the destination database and restart the task. For more information about how to modify the parameters of an ApsaraDB RDS for PostgreSQL instance, see Modify the parameters of an ApsaraDB RDS for PostgreSQL instance.

Possible cause 4: The destination index in the Elasticsearch cluster is generated after a rollover.

Solution: DTS does not support indexes that are generated after a rollover.

jobId=im6t3ajs21m****, code=03, errMsg=common: DTS-11005: framework: DTS-31008: fetch column info from target table dts_work.exercise_question_links failed
cause:
    AnyCoreException: framework: DTS-31008: fetch column info from target table dts_work.exercise_question_links failed
    NullPointerException: null

DTS-RETRY-ERR-0135: Packet for query is too large max_allowed_packet

Possible cause: The packet size exceeds the value of the max_allowed_packet parameter.

Solution: Make sure that the value of the max_allowed_packet parameter is greater than the packet size. Then, restart the task.

"framework: DTS-30011: currentRunningSQL: /* DTS-full-akl10d9m27u**** */insert ignore into `zeda`.`log`(`response_data`,`respond_message`,`ua_client`,`request_message`,`ip`,`module`,`ua_os`,`type`,`router`,`request_time`,`user_id`,`p_router`,`ua_device`,`response_time`,`id`,`api`,`username`) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?), reason: Packet for query is too large (74,694,508 > 67,108,864). You can change this value on the server by setting the 'max_allowed_packet' variable.
cause:
    BatchUpdateException: Packet for query is too large (74,694,508 > 67,108,864). You can change this value on the server by setting the 'max_allowed_packet' variable.
    PacketTooBigException: Packet for query is too large (74,694,508 > 67,108,864). You can change this value on the server by setting the 'max_allowed_packet' variable."

DTS-RETRY-ERR-0136: Get db all schemas error (.*)? Query execution was interrupted

Possible cause: The process of obtaining the schemas of the source database times out.

Solution: Restart the task.

DTS-1020009 Get db all schemas error,err msg:Query execution was interrupted, maximum statement execution time exceeded

DTS-RETRY-ERR-0137: Increment Context Is Not Running (.*)? DTS-52710 (.*)? log fetch failed

Possible cause: An error occurs when DTS pulls operation logs based on the timestamp.

jobId=x4l112aas19****, code=15, errMsg=dts-k-src: DTS-52111: Increment Context Is Not Running..:
cause:
    CriticalAnyAllException: mongo-reader: DTS-52710: log fetch failed
    CriticalAnyAllException: mongo-reader: DTS-52702: First Record Timestamp not correct, startPosition is : Timestamp{value=7160854279467565057, seconds=1667266311, inc=1}, record ts is : null

DTS-RETRY-ERR-0138: Increment Context Is Not Running (.*)? DTS-52233 (.*)? Invalid row format

Possible cause: The value of the binlog_format parameter is not row.

Solution: Set the value of the binlog_format parameter to row and run the KILL command to close all sessions in the source database. Then, reconfigure the task.

jobId=v2o117kyi13****, code=15, errMsg=dts-k-src: DTS-52111: Increment Context Is Not Running..:
cause:
    CriticalAnyAllException: mysql-reader: DTS-52210: fetch log failed
    IOException: mysql-reader: DTS-52233: Invalid row format : "INSERT INTO `apowo_manager_log` (`user`, `time`, `cname`, `c`, `m`, `uri`, `get`, `post`) VALUES ('zhangzhicheng', 1667284446, '****', 'activityconfig', 'repush', 'activityconfig/repush/22073', '[]', '[]')"
    CriticalAnyAllException: mysql-reader: DTS-52233: Invalid row format : "INSERT INTO `apowo_manager_log` (`user`, `time`, `cname`, `c`, `m`, `uri`, `get`, `post`) VALUES ('zhangzhicheng', 1667284446, '****', 'activityconfig', 'repush', 'activityconfig/repush/22073', '[]', '[]')"

DTS-RETRY-ERR-0139: Increment Context Is Not Running (.*)? First Record Timestamp not correct

Possible cause: The binary logs of the source database do not exist. As a result, DTS cannot collect incremental data.

Solution: Reconfigure the task.

\"bisId [e3g10360215****] run fail by [****], errorMsg:cluster [q4110pkw21t****] for channel [e3g10360215****] status [failed] is abnormal. errMsg:dts-k-src: DTS-52111: Increment Context Is Not Running..: \n" +
                "cause:\n" +
                "\tCriticalAnyAllException: mongo-reader: DTS-52710: log fetch failed\n" +
                "\tCriticalAnyAllException: mongo-reader: DTS-52702: First Record Timestamp not correct, startPosition is : Timestamp{value=7156853964107939841, seconds=1666334915, inc=1}, record ts is : null\"

DTS-RETRY-ERR-0140: Mirror Meta error (.*)? table or view does not exist

Possible cause 1: The table or view does not exist.

Solution: Check whether the corresponding table or view exists.

Possible cause 2: The database account that is used by the DTS task does not have the required permissions.

Solution: Check whether the database account that is used by the DTS task has the read permissions on the corresponding table or view.

jobId=s9v11f9at1f****, code=15, errMsg=dts-k-src: DTS-52102: retry final failed
cause:
    RecoverableAnyAllException: dts-k-src: DTS-52110: OracleRecordExtractor Init Error: oracle-reader: DTS-52050: Mirror Meta error,
    CriticalAnyAllException: oracle-reader: DTS-52050: Mirror Meta error,
    CriticalAnyAllException: oracle-reader: DTS-52050: Mirror meta failed
    CriticalAnyAllException: oracle-reader: DTS--0002: Can not create connection to source database, case by ORA-00942: table or view does not exist

    SQLSyntaxErrorException: ORA-00942: table or view does not exist

DTS-RETRY-ERR-0141: This type of SQL is not supported by group shard

Possible cause: The SQL statements that are executed in the source database are not supported by the destination database in group shard mode.

\"dts-k-src: DTS-52102: retry final failed\n" +
                "cause:\n" +
                "\tRecoverableAnyAllException: dts-k-src: DTS-52110: MySQLRecordExtractor Init Error: mysql-reader: DTS-52060: initial fetch position failed\n" +
                "\tCriticalAnyAllException: mysql-reader: DTS-52060: initial fetch position failed\n" +
                "\tIOException: java.sql.SQLException: Proxy ERROR: This type of SQL is not supported by group shard\n" +
                "\tSQLException: Proxy ERROR: This type of SQL is not supported by group shard\"

DTS-RETRY-ERR-0142: Specified key was too long

Possible cause: The maximum length of an index field in a table supported by the InnoDB engine of MySQL is 767 bytes.

Solution: For an instance of ApsaraDB RDS for MySQL V5.6 or 5.7, set the innodb_large_prefix parameter to ON. Then, reconfigure the task. For more information about how to modify instance parameters, see Modify instance parameters.

Specified key was too long; max key length is 767 bytes.

DTS-RETRY-ERR-0143: empty binlog list in oss

Possible cause: DTS cannot obtain the specified binary logs from Object Storage Service (OSS).

Solution: Contact Alibaba Cloud technical support.

id=35746****, jobId=dya1106628z****, value={"errMsg":"dts-k-src: DTS-52110: MySQLRecordExtractor Init Error: mysql-reader: DTS-52222: empty binlog list in oss, src rds instance = rm-bp1w2cl72i6in****, start time = 1669619166, end time = 1669905430","jobId":"t1d11sbo28z****","maxRetryTime":43200,"module":"reader","retryCount":30,"retryTarget":"srcDB","retryTime":1235,"retrying":true}

DTS-RETRY-ERR-0144: empty binlog list in

Possible cause: DTS cannot obtain the specified binary logs.

Solution: Contact Alibaba Cloud technical support.

id=357528****, jobId=udy119n2167*****, value={"errMsg":"dts-k-src: DTS-52110: MySQLRecordExtractor Init Error: mysql-reader: DTS-52222: empty binlog list in","jobId":"jer122l6i1j****","maxRetryTime":43200,"module":"reader","retryCount":2,"retryTarget":"srcDB","retryTime":592,"retrying":true}

DTS-RETRY-ERR-0145: Unknown column (.*)? in

Possible cause: The fields in the filter conditions that are configured for the task do not exist in the source database.

id=35746****, jobId=wzl12d7ie1g****, value={"errMsg":"framework: DTS-30020: execute sql:/* DTS-full-ykb12oe6k1n**** */SELECT `output`,`failed_times`,`input`,`created_time`,`biz_code`,`modified_time`,`next_exec_time`,`tx_id`,`biz_id`,`processor`,`tx_state` FROM `test_x7sy_com`.`sy_order_mgmt_local_tx_log` WHERE  ( create_time<1667232000 ) --> (null, null) record range id = 403027421250872****, fetchSize = -2147483648\ncause:\n\tMySQLSyntaxErrorException: Unknown column 'create_time' in 'where clause'","jobId":"ykb12oe6k1n****","maxRetryTime":43200,"module":"full","retryCount":110,"retryTarget":"srcDB","retryTime":1103,"retrying":true}

DTS-RETRY-ERR-0146: Connection reset

Possible cause: The connection between the task and the source database is reset.

Solution: Make sure that DTS can connect to the source database and restart the task.

id=35749****, jobId=j5h12gsco18****, value={"errMsg":"Connection reset ClientConnectionId:b7773844-5bf4-4439-83a7-f153f69f9601@error code:0","jobId":"cjs127rbb1k****","maxRetryTime":43200,"module":"reader","retryCount":61,"retryTarget":"srcDB","retryTime":915,"retrying":true}

DTS-RETRY-ERR-0147: You have an error in your SQL syntax

Possible cause: The fields in the filter conditions that are configured for the task do not exist in the source database.

id=35749****, jobId=k66125z4n1p****, value={"errMsg":"framework: DTS-30020: execute sql:/* DTS-full-aqb12ji5f1t**** */SELECT **** fetchSize = -2147483648\ncause:\n\tSQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ****}

DTS-RETRY-ERR-0148: You are not using binary logging

Possible cause: The MySQL database does not support the show binary logs command.

Solution: Update the version of the MySQL database and restart the task.

id=35757****, jobId=udy119n2167****, value={"errMsg":"You are not using binary logging@error code:1381","jobId":"jer122l6i1j****","maxRetryTime":43200,"module":"reader","retryCount":6,"retryTarget":"srcDB","retryTime":40,"retrying":true}

DTS-RETRY-ERR-0149: no partition for partitioning key

Possible cause: The corresponding shard of the field does not exist in the destination database.

Solution: Add the corresponding shard to the destination database and restart the task.

id=35756****, jobId=tlld17b825q****, value={"errMsg":"transaction-replicate: DTS-70004: execute statement failed: /*izmq1hx325617*****/insert into \"public\".\"order_req_pur_dt_his\" (\"bill_plu_id\",\"bill_no\",\"serial_no\",\"plu_id\",\"plu_code\",\"plu_name\",\"bar_code\",\"pack_id\",\"pack_code\",\"pack_name\",\"pack_rate\",\"unit\",\"pack_num\",\"pur_num\",\"audit_pack_num\",\"audit_num\",\"in_pur_price\",\"pur_in_total\",\"audit_in_total\",\"pur_type\",\"sal_price\",\"sal_total\",\"audit_sal_total\",\"stk_count\",\"udp1\",\"udp2\",\"remark\",\"rec_org_id\",\"pur_date\") values(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)\ncause:\n\tPSQLException: ERROR: no partition for partitioning key  (seg0 172.30.XX.XX:XXX pid=2776787)","jobId":"izmq1hx325617r6","maxRetryTime":1800,"module":"writer","retryCount":125,"retryTarget":"destDB","retryTime":1374,"retrying":true}

DTS-RETRY-ERR-0150: initial dictionary failed

Possible cause: DTS fails to connect to the source database. As a result, the DTS task fails to be initialized.

Solution: Make sure that DTS can connect to the source database and restart the task.

id=35755****, jobId=qs2p4wxqw83****, value={"errMsg":"dts-k-src: DTS-52110: MySQLRecordExtractor Init Error: mysql-reader: DTS-52051: initial dictionary failed","jobId":"zzo12r9zo1g****","maxRetryTime":7200,"module":"reader","retryCount":30,"retryTarget":"srcDB","retryTime":1136,"retrying":true}

DTS-RETRY-ERR-0151: The Network Adapter could not establish the connection

Possible cause: DTS fails to connect to the database due to a network issue.

Solution: Make sure that DTS can connect to the database and restart the task.

id=35755****, jobId=j16i46pbc63****, value={"errMsg":"IO Error: The Network Adapter could not establish the connection@error code:17002","jobId":"t1g12r9ka1q****","maxRetryTime":43200,"module":"reader","retryCount":47,"retryTarget":"srcDB","retryTime":1881,"retrying":true}

DTS-RETRY-ERR-0152: cannot open archived log (.*)? No such file or directory

Possible cause: The log file of the Oracle database does not exist.

Solution: Reconfigure the task.

id=35754****, jobId=tzv11059292****, value={"errMsg":"ORA-01284: file /sapdb/oracle/oraarch/EP2001/1_139037_1063496101.dbf cannot be opened\nORA-00308: cannot open archived log '/sapdb/oracle/oraarch/EP2001/1_139037_1063496101.dbf'\nORA-27037: unable to obtain file status\nLinux-x86_64 Error: 2: No such file or directory\nAdditional information: 7\nORA-06512: at \"SYS.DBMS_LOGMNR\", line 82\nORA-06512: at line 2\n@error code:","jobId":"q83122m2k19****","maxRetryTime":43200,"module":"reader","retryCount":11208,"retryTarget":"srcDB","retryTime":2999,"retrying":true}

DTS-RETRY-ERR-0154: odps (.*)? The specified partition does not exist

Possible cause: The table mentioned in the error message does not exist in the destination database.

Solution: Create a table in the destination database based on the error message and the information about the corresponding table in the source database. Then, restart the task.

jobId=n97107yf21k3bp8, code=07, errMsg=common: DTS-10009: transaction-replicate: DTS-70004: execute upload failed, may try it againcause:    RecoverableAnyAllException: transaction-replicate: DTS-70004: execute upload failed, may try it again    TransactionReplicateException: transaction-replicate: DTS-70003: 13 execute transaction has excess max transaction retry time [100] cause:odps: DTS-11014: Failed to get the upload session for cli_analytics.scene_template_codes_log caused by RequestId=2022120100085115d5d90b00f4ad31, ErrorCode=NoSuchPartition, ErrorMessage=The specified partition does not exist.RequestId=2022120100085115d5d90b00f4ad31, ErrorCode=NoSuchPartition, ErrorMessage=The specified partition does not exist.    CriticalAnyAllException: odps: DTS-11014: Failed to get the upload session for cli_analytics.scene_template_codes_log caused by RequestId=2022120100085115d5d90b00f****, ErrorCode=NoSuchPartition, ErrorMessage=The specified partition does not exist.RequestId=2022120100085115d5d90b00f4****, ErrorCode=NoSuchPartition, ErrorMessage=The specified partition does not exist.

DTS-RETRY-ERR-0155: OOM command not allowed when used memory

Possible cause: The destination Redis database is out of memory (OOM).

Solution: Increase the memory of the destination Redis database and restart the task. For more information about how to increase the memory of a Redis database, see Change the configurations of an instance.

jobId=vov11qjl30c****, code=04, errMsg=redis.clients.jedis.exceptions.JedisDataException: OOM command not allowed when used memory > 'maxmemory'.

DTS-RETRY-ERR-0156: This function has none of

Possible cause: The configurations of the database are incorrect.

Solution: Set the log_bin_trust_function_creators parameter to 1 and restart the task.

jobId=x9a11lf4308****, code=02, errMsg=This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)(advice: set the parameter log_bin_trust_function_creators = 1.). This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)(advice: set the parameter log_bin_trust_function_creators = 1.). This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)(advice: set the parameter log_bin_trust_function_creators = 1.). This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)(advice: set the parameter log_bin_trust_function_creators = 1.).

DTS-RETRY-ERR-0157: Incorrect column name

Possible cause: The column name in the objects to be synchronized or migrated contains special characters, such as spaces.

Solution: Modify the column name and restart the task.

jobId=or81144k303****, code=02, errMsg=[13000, 202211302315061921681441470345301****] Incorrect column name: ` 一级ç.

DTS-RETRY-ERR-0158: Failed to get global table lock for

Possible cause: Multiple tables cannot be managed in one transaction in the current database.

Solution: Contact Alibaba Cloud technical support.

jobId=q8k11raf309****, code=03, errMsg=common: DTS-11005: framework: DTS-31008: fetch column info from target table snt8888_eb.amazon_ad_keywords_report_detail failedcause:    AnyCoreException: framework: DTS-31008: fetch column info from target table snt8888_eb.amazon_ad_keywords_report_detail failed    CriticalAnyAllException: full-mysql: DTS-61008: Fetch meta info failed    SQLException: Failed to get global table lock for 'snt8888_eb.amazon_ad_keywords_report_detail'jobId=q8k11raf309k04d, code=03, errMsg=common: DTS-11005: framework: DTS-31008: fetch column info from target table ajcx_wms.4px_oda failedcause:    AnyCoreException: framework: DTS-31008: fetch column info from target table ajcx_wms.4px_oda failed    CriticalAnyAllException: full-mysql: DTS-61008: Fetch meta info failed    SQLException: Failed to get global table lock for 'ajcx_wms.4px_oda'

DTS-RETRY-ERR-0159: Column (.*)? cannot be null

Possible cause: The column in the destination database has the NOT NULL constraint. As a result, an error occurs when a NULL value is written to the column.

Solution: Remove the NOT NULL constraint from the column.

jobId=ccf11aiz18j****, code=04, errMsg=DTS-077105: Record Replicator error in table CARGONEST_RATE.SCYX_FLIGHT. cause by [java.sql.SQLIntegrityConstraintViolationException: Column 'USE' cannot be null] About more information in ****

DTS-RETRY-ERR-0161: First Record Timestamp not correct

Possible cause: An error occurs when DTS queries the logs of a consumption checkpoint.

Solution: Check the status of the logs. If the status is abnormal, fix the logs and restart the task. If the status is normal, reconfigure the task.

jobId=eq2126nwc16****, code=15, errMsg=dts-k-src: DTS-52111: Increment Context Is Not Running..: cause:    CriticalAnyAllException: mongo-reader: DTS-52710: log fetch failed    CriticalAnyAllException: mongo-reader: DTS-52702: First Record Timestamp not correct, startPosition is : Timestamp{value=7171932524837339137, seconds=1669845666, inc=1}, record ts is : null

DTS-RETRY-ERR-0162: cannot find index by table

Possible cause: The specified index does not exist in the Elasticsearch cluster.

Solution: Manually create an index in the Elasticsearch cluster and restart the task.

jobId=v3w11of923k****, code=03, errMsg=common: DTS-11005: framework: DTS-31008: fetch column info from target table operation.inspection_product_index/inspection_product failedcause:    AnyCoreException: framework: DTS-31008: fetch column info from target table operation.inspection_product_index/inspection_product failed    RuntimeException: es: DTS-11014: can not find index by table=inspection_product_index, schema=null, database=operation, mapping=inspection_product    CriticalAnyAllException: es: DTS-11014: can not find index by table=inspection_product_index, schema=null, database=operation, mapping=inspection_product

DTS-RETRY-ERR-0163: The sts token is denied

Possible cause: The Security Token Service (STS) token expires.

Solution: Restart the task.

jobId=nspj5ej820r****, code=07, errMsg=nosql-replicate: DTS-70004: execute statement failedcause:    NoPermissionException: [httpStatus:403, requestId:20221201101811180ec50b2153****, errorCode:NoPermission, errorMessage:The sts token is denied: STS.NUvD4Yo4qGKZ1jhhM662g****]

DTS-RETRY-ERR-0164: Too many connections

Possible cause: The number of connections to the database has reached the upper limit.

Solution: Check the maximum number of connections to the database and the current number of connections to the database. Modify the database configurations based on your business requirements. For example, you can modify the max_connections parameter to change the maximum number of connections. Then, restart the task.

jobId=yof12l14o19****8635, code=03, errMsg=jdbc-burst: DTS-61015: Create connection failed (url: 172.18.XX.XX:XXX, user: yj_gusb_root)cause:    MySQLNonTransientConnectionException: Too many connections

DTS-RETRY-ERR-0165: seek binlog for timestamp (.*)? not exits

Possible cause: The binary logs of the source MySQL database are cleared.

jobId=sptc8p3x129****, code=15, errMsg=dts-k-src: DTS-52102: retry final failedcause:    RecoverableAnyAllException: dts-k-src: DTS-52110: MySQLRecordExtractor Init Error: mysql-reader: DTS-52212: MySQL binlog 1660282274 is not exists.    CriticalAnyAllException: mysql-reader: DTS-52212: MySQL binlog 1660282274 is not exists.    IOException: java.sql.SQLException: seek binlog for timestamp 1660282274, not exits.    SQLException: seek binlog for timestamp 1660282274, not exits.

DTS-RETRY-ERR-0167: the Table (.*)? Information Loaded failed in Target DB

Possible cause: A specific schema does not exist in the destination database.

Solution: Make sure that the schema exists in the destination database and the configurations of the task are correct. Then, restart the task.

jobId=lg612z5iq1x****, code=07, errMsg=DTS-071001: the Table anta_mw_stock_prod.stk_virtualstocklocklog Information Loaded failed in Target DB. cause by [[17001, 2022120116320501021111713303151290766] schema not exist => anta_mw_stock_prod] About more information in ****

DTS-RETRY-ERR-0168: A UNIQUE INDEX must include all columns in the table's partitioning function

Possible cause: A unique index does not include all columns in the partitioning function.

Solution: Modify the unique index to include all columns in the partitioning function.

jobId=beu12x8vd1l****, code=02, errMsg=A UNIQUE INDEX must include all columns in the table's partitioning function. 

DTS-RETRY-ERR-0169: Can not find where column (.*)? in before image of record

Possible cause: The clustered index does not include a primary key column. When you execute the UPDATE statement on an SQL Server database, only the pre-image values can be parsed.

Solution: Modify the clustered index to include the primary key column, and restart the task.

id=35938****, jobId=slr122e2h5y****, value={"errMsg":"transaction-framework: DTS-70029: Can not find where column  in before image of record LazyParseRecord {offset [465035], operationType [UPDATE], checkpoint [0@483462@0008b7dd:00019ab8:0002@1670195470000]}","jobId":"jqr12oeww55****","maxRetryTime":43200,"module":"writer","retryCount":19,"retryTarget":"destDB","retryTime":182,"retrying":true}

DTS-RETRY-ERR-0170: Cannot insert duplicate key row in object

Possible cause: The write operation fails due to a primary key conflict caused by an enabled trigger.

Solution: Disable or delete the trigger and restart the task.

id=35945****, jobId=p2611skq18s****, value={"errMsg":"transaction-replicate: DTS-70004: execute statement failed: /*dc4112pf18696rtSQLServerPrepareStatementSqlEngine(23)*/insert into [zjnb].[dbo].[yw_hddz_fsdz]([dzdm], [cxh], [dzbh], [id], [ywbh], [bgid]) values(?, ?, ?, ?, ?, ?)\ncause:\n\tSQLServerException: Cannot insert duplicate key row in object 'dbo.yw_hddz_fsdz' with unique index 'yw_hddz_fsdz_index'. The duplicate key value is (22DP01833, 0).","jobId":"dc4112pf186****","maxRetryTime":1800,"module":"writer","retryCount":98,"retryTarget":"destDB","retryTime":1511,"retrying":true}

DTS-RETRY-ERR-0171: The server experienced an unexpected error when processing the request

Possible cause: The incremental data collection module is abnormal.

Solution: Contact Alibaba Cloud technical support.

id=35956****, jobId=kk411xezf49****, value={"errMsg":"dts-k-src: DTS-52122: Error on Send.The server experienced an unexpected error when processing the request","jobId":"vag1121af47****","maxRetryTime":43200,"module":"reader","retryCount":0,"retryTarget":"dstore","retryTime":1,"retrying":true}

DTS-RETRY-ERR-0172: The INSERT statement conflicted with the FOREIGN KEY constraint

Possible cause: The write operation fails because the destination database contains an enabled foreign key.

Solution: Disable or delete the foreign key and restart the task.

id=35955****, jobId=s0s12libr5m****, value={"errMsg":"common: DTS-11005: The INSERT statement conflicted with the FOREIGN KEY constraint \"file_qc_number_testing_id_a9e3abb7_fk_dimension_testing_testing_id\". The conflict occurred in database \"tyDbTest\", table \"dbo.dimension_testing\", column 'testing_id'.\ncause:\n\tBatchUpdateException: The INSERT statement conflicted with the FOREIGN KEY constraint \"file_qc_number_testing_id_a9e3abb7_fk_dimension_testing_testing_id\". The conflict occurred in database \"tyDbTest\", table \"dbo.dimension_testing\", column 'testing_id'.","jobId":"rn9120w5g5k****","maxRetryTime":43200,"module":"full","retryCount":49,"retryTarget":"destDB","retryTime":1751,"retrying":true}

DTS-RETRY-ERR-0173: unsupported value convert for

Possible cause: DTS cannot perform type conversion because the schemas of tables in the source and destination databases are inconsistent.

Solution: Modify the schema of the table in the destination database to be the same as that in the source database. Then, restart the task.

id=35955****, jobId=a1s126u5s54****, value={"errMsg":"jdbc-utils: DTS-11001: jdbc-utils: DTS-11001: Adb30StringDisperse: unsupported value convert for [2023-01-01 01:00:00] convert to [create_time DATE nullable as create_time] targetDatabase:crm targetTable:orders\ncause:\n\tJdbcUtilsException: jdbc-utils: DTS-11001: Adb30StringDisperse: unsupported value convert for [2023-01-01 01:00:00] convert to [create_time DATE nullable as create_time]","jobId":"c28120pby5n****","maxRetryTime":43200,"module":"writer","retryCount":223,"retryTarget":"destDB","retryTime":2240,"retrying":true}

DTS-RETRY-ERR-0174: ETL (.*)? not found in

Possible cause: The data processing statement for ETL is incorrect.

Solution: Use the table name and column name of the source database in the data processing statement. Then, restart the task. For more information about how to modify the ETL configurations, see Configure ETL in a data migration or data synchronization task.

jobId=x9611z8z28s****, code=07, errMsg=framework: DTS-31009: In process of processing data (recordRange: 572237829218343****) failedcause:    CriticalAnyAllException: ETL: DTS--0001: Error while executing user ETL: dt_now not found in fillmed_import.membership_customer_detail    RuntimeException: dt_now not found in fillmed_import.membership_customer_detail

DTS-RETRY-ERR-0175: Connect db failure

Possible cause: DTS fails to connect to the source database.

Solution: Check whether the information and configurations of the source database are correct. For more information, see Source database connectivity.

jobId=hedw7wu7z60****, code=02, errMsg=DTS-002003 Connect db failure, unknow db url jdbc:postgresql://100.100.XX.XX:XXX/testdb, please vaild url. Original error: The connection attempt failed. For more information please refer to ****

DTS-RETRY-ERR-0176: too many connections for role

Possible cause: The number of connections to the database has reached the upper limit.

Solution: Check the maximum number of connections to the database and the current number of connections to the database. Modify the database configurations based on your business requirements. For example, you can modify the max_connections parameter to change the maximum number of connections. Then, restart the task.

jobId=yyh128cwc5h****, code=02, errMsg=init job fail FATAL: too many connections for role "inventory_prod_ad_readonly"

DTS-RETRY-ERR-0177: numeric field overflow

Possible cause: The schemas of tables in the source and destination databases are inconsistent.

Solution: Modify the schemas of tables in the destination database to be the same as those in the source database. Then, restart the task.

jobId=er411gx1251****, code=03, errMsg=full-greenplum: DTS-65708: copy error, recordRange= **** cause:    PSQLException: ERROR: numeric field overflow ****

DTS-RETRY-ERR-0178: JedisDataException (.*)? ERR (.*)? command keys must in same slot

Possible cause: The passed keys are not allocated in the same hash slot.

Solution: The passed keys must be allocated in the same hash slot. This ensures the atomicity of a transaction in a Lua script. Modify the Lua script and restart the task.

jobId=xd6121n2d5e****, code=04, errMsg=redis.clients.jedis.exceptions.JedisDataException: ERR 'EVAL' command keys must in same slot

DTS-RETRY-ERR-0179: ADB30Engine (.*)? COMMA is not value type

Possible cause: An SQL syntax error occurs because COMMA is not a valid data type.

Solution: Modify the invalid SQL statement and restart the task.

jobId=chzi9boc27z****, code=07, errMsg=transaction-replicate: DTS-70004: execute statement failed: /*dts_id=dtsc0pg9ems27y*****/replace into `inhouse`.`grain_category_template` **** error detail message:[15018, 202212051752081921681240150345324****] syntax error :syntax error => COMMA is not value type, pos:558 row: 0 and ceil:1    SQLException: [15018, 202212051752081921681240150345324****] syntax error :syntax error => COMMA is not value type, pos:558 row: 0 and ceil:1

DTS-RETRY-ERR-0180: Schema matched failed

Possible cause: The schemas of tables in the source and destination databases are inconsistent.

jobId=iicu948h28d****, code=07, errMsg=DTS-071007: Schema matched failed. cause by [Can not find column TSSQQKSM_DM<-->tssqqksm_dm[true] in target table table_group_zrryh_mx.f_rt_zs_tdssq_qccx] About more information in ****

DTS-RETRY-ERR-0181: invalid hexadecimal digit

Possible cause: The SQL statement contains an invalid hexadecimal value.

Solution: Modify the invalid SQL statement and restart the task.

jobId=i9c12l3kn1m****, code=03, errMsg=full-postgresql: DTS-65708: copy error, recordRange={id:364619936051914****,schema:saasv4.C_REPORT,indexName:,fields:[DJNAME STRING nullable unique],leftValues:[null],rightValues:[null],partition:null}, copySql=/* DTS-full-i9c12l3kn1m**** *//* DTS-full-i9c12l3kn1m**** */COPY "saasv4".c_report ("fanganid","fanganname","fangandes","djname","updated","fangan") FROM STDIN DELIMITER '|' ESCAPE '\' CSV QUOTE '"'cause:    PSQLException: ERROR: invalid hexadecimal digit: "<"  Where: COPY c_report, line 1, column fangan: "<?xml version="1.0" encoding="utf-8"?>\015\012<TfrxReport Version="4.3" DotMatrixReport="False" IniF..."

DTS-RETRY-ERR-0182: command denied to user

Possible cause 1: The database account that is used by the DTS task does not have the required permissions.

Possible cause 2: The database mentioned in the error message is a system database, such as the sys database, or a database that does not need to be synchronized or migrated.

jobId=sj112p70c50****, code=02, errMsg=REFERENCES command denied to user 'qianyi_dts'@'100.104.XX.XX' for table 'dbdj_lance.extauth_user'. ****

DTS-RETRY-ERR-0183: MySQL table (.*)? binlog column count check error

Possible cause: The number of columns in the table mentioned in the error message in binary logs is not the same as that in DTS.

jobId=oh9111i723x****, code=15, errMsg=dts-k-src: DTS-52111: Increment Context Is Not Running..: mysql-reader: DTS-52210: fetch log failedcause:    IOException: mysql-reader: DTS-52234: MySQL table dxl_shops.sys_module binlog column count check error, local count is 0, but binlog count is 15, at offset 162@25064****.    CriticalAnyAllException: mysql-reader: DTS-52234: MySQL table dxl_shops.sys_module binlog column count check error, local count is 0, but binlog count is 15, at offset 162@25064****.

DTS-RETRY-ERR-0184: CLIENT_PLUGIN_AUTH is required

Possible cause: DTS fails to connect to the database.

Solution: Check the version of the MySQL database. For more information about the supported MySQL database versions, see Overview of data synchronization scenarios, Overview of data migration scenarios, and Overview of change tracking scenarios.

id=36512****, jobId=r5e120d1u5u****, value={"errMsg":"CLIENT_PLUGIN_AUTH is required@error code:0","jobId":"xu812lh7i5p****","maxRetryTime":43200,"module":"reader","retryCount":745,"retryTarget":"srcDB","retryTime":9911,"retrying":true}

DTS-RETRY-ERR-0185: ADB30Engine (.*)? For input string

Possible cause: The schema of the table in the destination database mentioned in the error message is incompatible with the values in the source database.

Solution: Change the type of the column in the destination database to be the same as that in the source database. Then, restart the task.

jobId=ugui7hl1h83****, code=07, errMsg=transaction-replicate: DTS-70004: execute statement failed: /*dts_id=dtserev7v26j8i*****/replace into `ylh_order`.`recycle_standing_book` **** cause:    SQLException: ADB30Engine(15): meet error, insertSQL:/*dts_id=dtserev7v26j8i*****/replace into `ylh_order`.`recycle_standing_book` **** error detail message:[15018, 202212160839511921682250660315152****] (Column => RECYCLE_STANDING_BOOK.DB_ID), For input string: "14033071031736****"    SQLException: [15018, 202212160839511921682250660315152****] (Column => RECYCLE_STANDING_BOOK.DB_ID), For input string: "14033071031736****"

DTS-RETRY-ERR-0186: not authorized on (.*)? to execute command

Possible cause: The database account that is used by the DTS task does not have the required permissions.

• Solution 1: Grant the required permissions to the database account and restart the task.

• Solution 2: Configure the task by using a database account with the required permissions.

jobId=j99123a7161****, code=03, errMsg=common: DTS-11005: com.mongodb.MongoCommandException: Command failed with error 13: 'not authorized on zcscenter_log to execute command { insert: "UserBehaviorLog", ordered: true, bypassDocumentValidation: true, $db: "zcscenter_log" }' on server 172.16.XX.XX:XXX. The full response is { "operationTime" : { "$timestamp" : { "t" : 1671158607, "i" : 1 } }, "ok" : 0.0, "errmsg" : "not authorized on zcscenter_log to execute command { insert: \"UserBehaviorLog\", ordered: true, bypassDocumentValidation: true, $db: \"zcscenter_log\" }", "code" : 13, "codeName" : "Unauthorized", "$clusterTime" : { "clusterTime" : { "$timestamp" : { "t" : 1671158607, "i" : 1 } }, "signature" : { "hash" : { "$binary" : "FMyelyFIm+zD****/XOiGFd****=", "$type" : "00" }, "keyId" : { "$numberLong" : "717355978057161****" } } } } **** 

DTS-RETRY-ERR-0187: The TCP/IP connection to the host (.*)? has failed

Possible cause: The connection to a database fails.

Solution: Troubleshoot the error based on the error message. If the error persists, contact Alibaba Cloud technical support.

jobId=vtsv5pgl22m****, code=03, errMsg=common: DTS-11005: framework: DTS-31008: fetch column info from source table [EMWSHANGHAI].[dbo].[OILM] failedcause:    AnyCoreException: framework: DTS-31008: fetch column info from source table [EMWSHANGHAI].[dbo].[OILM] failed    RuntimeException: jdbc-burst: DTS-61015: Create connection failed (url: 172.16.XX.XX:XXX, user: sa)cause:    SQLServerException: The TCP/IP connection to the host 172.16.XX.XX, port XXX has failed. Error: "The driver received an unexpected pre-login response. Verify the connection properties and check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. This driver can be used only with SQL Server 2005 or later.". ****

DTS-RETRY-ERR-0188: null value in column (.*)? violates not-null constraint

Possible cause: A column with the NOT NULL constraint in the destination database is filtered out, or the value of the corresponding column in the source database is NULL.

Solution: Make sure that the object to be synchronized or migrated meets the constraint in the destination database. Then, restart the task.

jobId=hn612sbb16q****, code=03, errMsg=full-greenplum: DTS-65708: copy error, recordRange={id:266622423602823****,schema:ods_ecology1.workflow_yozotopdfconfig,indexName:,fields:[],leftValues:[null],rightValues:[null],partition:null}, copySql=/* DTS-full-hn612sbb16q**** *//* DTS-full-hn612sbb16q**** */COPY "ods_ecology1"."workflow_yozotopdfconfig" ("useWps","useyozo") FROM STDIN DELIMITER '|' ESCAPE '\' CSV QUOTE '"' DO on conflict DO update cause:    PSQLException: ERROR: null value in column "useWps" violates not-null constraint  Detail: Failing row contains (0, null).  Where: COPY workflow_yozotopdfconfig, line 1

DTS-RETRY-ERR-0189: ON CONFLICT DO UPDATE command cannot affect row a second time

Possible cause: The unique indexes of the source and destination databases are inconsistent.

Solution: Modify the indexes based on your business requirements. Make sure that the unique indexes of the source and destination databases are consistent. Then, restart the task.

jobId=hn612sbb16q****, code=03, errMsg=full-greenplum: DTS-65708: copy error, recordRange={id:664004810422773****,schema:ods_ecology1.workflow_requestlog,indexName:,fields:[LOGID INTEGER not nullable],leftValues:[null],rightValues:[null],partition:null}, copySql=/* DTS-full-hn612sbb16q**** *//* DTS-full-hn612sbb16q**** */COPY "ods_ecology1"."workflow_requestlog" ("OPERATORDEPT","OPERATEDATE","speechattachmente9","isSubmitDirect","uuid","NODEID","SIGNDOCIDS","REMARKLOCATION","clientip","SHOWORDER","ANNEXDOCIDS","SIGNWORKFLOWIDS","AGENTTYPE","REMARK","RECEIVEDPERSONS_1","seclevel","SPEECHATTACHMENT","LOGTYPE","RECEIVEDPERSONS","REMARK1","OPERATETIME","operatorJob","DESTNODEID","OPERATORTYPE","LOGID","operatorSub","remarkquote","fulltextannotation","isRobotNode","REQUESTLOGID","RECEIVEDPERSONIDS","WORKFLOWID","OPERATOR","ISMOBILE","AGENTORBYAGENTID","HandWrittenSign","REQUESTID") FROM STDIN DELIMITER '|' ESCAPE '\' CSV QUOTE '"' DO on conflict DO update cause:    PSQLException: ERROR: ON CONFLICT DO UPDATE command cannot affect row a second time  Hint: Ensure that no rows proposed for insertion within the same command have duplicate constrained values.  Where: COPY workflow_requestlog, line 6

DTS-RETRY-ERR-0190: There is no column (.*)? in table

Possible cause: A column does not exist in the destination table.

Solution: Add the missing column to the specified table of the destination database based on the schema of the table in the source database and error message. Then, restart the task.

jobId=t0q12vjgl98****, code=07, errMsg=DTS-077100: Record Replicator error in table uat_r3_oms_oc_ip.oc_b_tob_order. cause by [com.alibaba.amp.increment.exception.AmpException: There is no column `echo_status` in table `r3_rc_datasync`.`oc_b_tob_order`] About more information in ****

DTS-RETRY-ERR-0191: Host (.*)? is blocked because of many connection

Possible cause: The number of connections to the database has reached the upper limit.

Solution: Check the maximum number of connections to the database and the current number of connections to the database. Modify the database configurations based on your business requirements. For example, you can modify the max_connections parameter to change the maximum number of connections. Then, restart the task.

jobId=kv512kmj15n****, code=03, errMsg=common: DTS-11005: framework: DTS-31008: fetch column info from source table shineserver.tbl_invdata_d_2023_01_07 failedcause:    AnyCoreException: framework: DTS-31008: fetch column info from source table shineserver.tbl_invdata_d_2023_01_07 failed    CriticalAnyAllException: full-mysql: DTS-00000: Fetch meta info failed    DBCommonException: jdbc-burst: DTS-61015: Create connection failed (url: 172.27.XX.XX:XXX, user: root)    SQLException: null,  message from server: "Host '100.104.XX.XX' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts'"

DTS-RETRY-ERR-0192: Get all databases in (.*)? DB failed

Possible cause: An error occurs when DTS queries the information about the source database.

Solution: Make sure that the status of the source database is normal and the source database can be connected. Then, restart the task.

jobId=mmbg34h530g****, code=04, errMsg=DTS-070611: Get all databases in v5x0617 DB failed. Source

DTS-RETRY-ERR-0193: schema (.*)? does not exist

Possible cause: The schema does not exist in the source or destination database.

Solution: Make sure that the schema mentioned in the error message exists in the source and destination databases. Then, restart the task.

jobId=tycy1xi5d4w****, code=03, errMsg=full-greenplum: DTS-65708: copy error, recordRange={id:65629572036558****,schema:dtstest.master_ld_pg_test,indexName:,fields:[id BIGINT not nullable primary unique],leftValues:[null],rightValues:[null],partition:null}, copySql=/* DTS-full-tycy1xi5d41**** *//* DTS-full-tycy1xi5d4w**** */COPY "dtstest"."master_ld_pg_test" ("name","id","name2") FROM STDIN DELIMITER '|' ESCAPE '\' CSV QUOTE '"' DO on conflict DO update cause:    PSQLException: ERROR: schema "" does not exist  (seg0 172.25.XX.XX:XXX pid=556)

DTS-RETRY-ERR-0194: WRONGPASS invalid username-password pair or user is disabled

Possible cause: The account or password of the Redis database is incorrect.

Solution: Use the correct account and password to configure the task.

jobId=yji127k830v****, code=04, errMsg=redis: DTS-10015: redis: DTS-10010: WRONGPASS invalid username-password pair or user is disabled.cause:    RedisClientInitiationException: redis: DTS-10010: WRONGPASS invalid username-password pair or user is disabled.

DTS-RETRY-ERR-0195: Create Table Exceed limit

Possible cause: The number of topics in the destination DataHub project has reached the upper limit.

Solution: Delete invalid topics and restart the task. For more information about how to delete a topic, see Manage topics.

jobId=gta119cz22v****, code=02, errMsg=DTS-1029999 The ddlmove task gta119cz22vg6d4 was finished,but 598 objects failed,error message:[DTS]Create Table Exceed limit, max topics for one project is 500, current is 500 in dts (Status Code: 400; Error Code: ResourceLimit; Request ID: 20230111104946510ec50bfb87****),[DTS]Create Table Exceed limit, max topics for one project is 500, current is 500 in dts (Status Code: 400; Error Code: ResourceLimit; Request ID: 202301111049445d0ec50bfb83****),[DTS]Create Table Exceed limit, max topics for one project is 500, current is 500 in dts (Status Code: 400; Error Code: ResourceLimit; Request 

DTS-RETRY-ERR-0196: user (.*)? does not exist

Possible cause 1: The table or view does not exist.

Solution: Add the corresponding table or view based on the error message and restart the task.

Possible cause 2: The database account that is used by the DTS task does not have the required permissions.

Solution: Grant the required permissions to the database account and restart the task.

jobId=ssbc18z7113****, code=02, errMsg=ORA-01918: user 'BOND_EXT_ETL' does not exist. ORA-00942: table or view does not exist

DTS-RETRY-ERR-0197: table or view does not exist

Possible cause 1: The table or view does not exist.

Solution: Add the corresponding table or view based on the error message and restart the task.

Possible cause 2: The database account that is used by the DTS task does not have the required permissions.

Solution: Grant the required permissions to the database account and restart the task.

jobId=ssbc18z7113****, code=02, errMsg=ORA-01918: user 'BOND_EXT_ETL' does not exist. ORA-00942: table or view does not exist

DTS-RETRY-ERR-0198: FUNCTION (.*)? does not exist

Possible cause: The view or function to be migrated depends on other objects. As a result, DTS fails to create the view or function.

Solution: Modify the view or function by removing the dependencies. Then, restart the schema migration module. If the error persists, contact Alibaba Cloud technical support.

jobId=n37x1mlh115****, code=02, errMsg=FUNCTION riskcenter.fn_GetCustName does not exist. FUNCTION riskcenter.fn_GetMemLoginName does not exist. FUNCTION riskcenter.fn_GetDistName does not exist. FUNCTION riskcenter.fn_GetCustName does not exist. FUNCTION riskcenter.fn_GetCustName does not exist. FUNCTION riskcenter.fn_GetCustName does not exist. FUNCTION riskcenter.fn_GetCustName does not exist. FUNCTION riskcenter.fn_GetCustName does not exist. FUNCTION riskcenter.fn_GetCustName does not exist. FUNCTION riskcenter.fn_GetCustName does not exist. FUNCTION riskcenter.fn_GetCustName does not exist. FUNCTION riskcenter.fn_GetCustName does not exist. FUNCTION riskcenter.fn_GetMemLoginName does not exist. FUNCTION riskcenter.fn_GetCustName does not exist. FUNCTION riskcenter.fn_GetCustName does not exist. FUNCTION riskcenter.fn_GetDistName does not exist. FUNCTION riskcenter.fn_GetCustName does not exist. FUNCTION riskcenter.fn_GetCustName does not exist. FUNCTION riskcenter.fn_GetCustName does not exist. FUNCTION riskcenter.fn_GetCustName does not exist.

DTS-RETRY-ERR-0199: fetch column info from source table (.*)? failed

Possible cause: The connection to the source database is abnormal. As a result, DTS fails to query the corresponding column information from the source database.

Solution: Restart the task. If the error persists, contact Alibaba Cloud technical support.

jobId=vtsv5pgl22m7****, code=03, errMsg=common: DTS-11005: framework: DTS-31008: fetch column info from source table [EMWSHANGHAI].[dbo].[OILM] failedcause:    AnyCoreException: framework: DTS-31008: fetch column info from source table [EMWSHANGHAI].[dbo].[OILM] failed    RuntimeException: jdbc-burst: DTS-61015: Create connection failed (url: 172.16.XX.XX:XXX, user: sa)cause:    SQLServerException: Connection reset ClientConnectionId:b2bb965c-e92a-4311-b499-cff270ff****    SocketException: Connection reset    DBCommonException: jdbc-burst: DTS-61015: Create connection failed (url: 172.16.XX.XX:XXX, user: sa)    SQLServerException: Connection reset ClientConnectionId:b2bb965c-e92a-4311-b499-cff270ff****    SocketException: Connection reset

DTS-RETRY-ERR-0200: value too large for column

Possible cause: The length of the data to be written has reached the upper limit of the field that is configured in the schema.

Solution: Modify the maximum length of the field based on your business requirements. Then, restart the task.

jobId=ckwu1nn2100****, code=07, errMsg=common: DTS-100047: retry 4151 times, 43201510 seconds, which exceed the supposed 43200 secondscause:    TransactionReplicateException: transaction-replicate: DTS-70004: execute statement failed: /*ckwu1nn210048jjOraclePrepareStatementSqlEngine(14)*/insert into ****     SQLException: ORA-12899: value too large for column "XFS_OPEN_PLATFORM_EX"."T_PRODUCT_CHANNEL"."CHANNEL_NAME" (actual: 38, maximum: 32)

DTS-RETRY-ERR-0201: Can not find column (.*)? in target table

Possible cause: A column does not exist in the destination table.

Solution: Add the missing column to the specified table of the destination database based on the schema of the table in the source database and error message. Then, restart the task.

jobId=zhml16az11q****, code=07, errMsg=DTS-071007: Schema matched failed. cause by [Can not find column bpmSn<-->bpmSn[true] in target table anta_mw_order_prod.bas_warehouse] About more information in ****

DTS-RETRY-ERR-0203: Table (.*)? does not exist

Possible cause: Some tables do not exist in the source or destination database.

jobId=x3dl1cbm11r****, code=03, errMsg=common: DTS-11005: framework: DTS-31008: fetch column info from target table tms_service2.tp_3286333_ogl_logistics_trajectory_2 failedcause:    AnyCoreException: framework: DTS-31008: fetch column info from target table tms_service2.tp_3286333_ogl_logistics_trajectory_2 failed    RuntimeException: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: [17003, 202301110800570100020000460315122****] Table adb.tms_service2.tp_3286333_ogl_logistics_trajectory_2 does not exist

DTS-RETRY-ERR-0204: Disk full (.*)? waiting for someone to free some space

Possible cause: The disk space of the destination database is full.

Solution: Extend the disk for the destination database and restart the task.

jobId=h03q1pas10o****, code=03, errMsg=framework: DTS-30011: currentRunningSQL: /* DTS-full-h03q1pas10o**** */insert ignore into **** cause:    BatchUpdateException: Disk full (tb_ms_video_collect_day_20221221); waiting for someone to free some space... (errno: 189 "Disk full")    SQLException: Disk full (tb_ms_video_collect_day_20221221); waiting for someone to free some space... (errno: 189 "Disk full")    Disk full **** waiting for someone to free some space

DTS-RETRY-ERR-0209: relation (.*)? does not exist

Possible cause: The relationship does not exist in the destination database.

Solution: Establish a relationship in the destination database based on the error message. Then, restart the task.

id=37908****, jobId=eo3m1z6t11y****, value={"errMsg":"java.lang.RuntimeException: Table '`wk_crm`.`wk_examine_advanced_config`' with columns [`create_user_id`, `node_handle_type`, `modify_permission_type`, `create_time`, `company_id`, `limit_time_status`, `batch_id`, `advanced_config_id`, `examine_id`, `update_time`, `node_handle_user`, `update_user_id`, `reject_handle_type`, `repeat_handle_type`] and batch exception is {[13000, 202301110018191921681780610345332****] (Column => WK_EXAMINE_ADVANCED_CONFIG.NODE_HANDLE_USER), For input string: ****

DTS-RETRY-ERR-0212: batch exception (.*)? For input string

Possible cause: The type of data to be written to the destination database is different from the data type defined in the schema.

Solution: Modify the schema of the table in the destination database to be the same as that in the source database. Then, restart the task.

id=37908****, jobId=eo3m1z6t11y****, value={"errMsg":"java.lang.RuntimeException: Table '`wk_crm`.`wk_examine_advanced_config`' with columns [`create_user_id`, `node_handle_type`, `modify_permission_type`, `create_time`, `company_id`, `limit_time_status`, `batch_id`, `advanced_config_id`, `examine_id`, `update_time`, `node_handle_user`, `update_user_id`, `reject_handle_type`, `repeat_handle_type`] and batch exception is {[13000, 202301110018191921681780610345332****] (Column => WK_EXAMINE_ADVANCED_CONFIG.NODE_HANDLE_USER), For input string: \"161281865257152****,161281865208498****\"}","jobId":"t2pa1xp1112****","maxRetryTime":43200,"module":"full","retryCount":9,"retryTarget":"destDB","retryTime":80,"retrying":true}

DTS-RETRY-ERR-0213: mapper (.*)? of different type

Possible cause: The type of data to be written to the destination database is different from the data type defined in the schema.

Solution: Modify the schema of the table in the destination database to be the same as that in the source database. Then, restart the task.

PUT **** {  "error" : {    "root_cause" : [      {        "type" : "illegal_argument_exception",        "reason" : "mapper [user_disease_point_id] of different type, current_type [text], merged_type [long]"      }    ],    "type" : "illegal_argument_exception",    "reason" : "mapper [user_disease_point_id] of different type, current_type [text], merged_type [long]"  },  "status" : 400}

DTS-RETRY-ERR-0214: Stream closed

Possible cause: The network connection times out.

Solution: Make sure that the status of the source database is normal and the source database can be connected. Then, restart the task.

**** framework: DTS-31009: In process of processing data (recordRange: 827160178650303****) failedcause:RedisServerException: redis: DTS-10015: redis: DTS-10009: Stream closedRedisCannotRetryException: redis: DTS-10009: Stream closedIOException: Stream closed ****

DTS-RETRY-ERR-0215: wait millis (.*)? active (.*)? maxActive

Possible cause: DTS fails to connect to the database.

Solution: Restart the task. If the error persists, contact Alibaba Cloud technical support.

**** wait millis 300000, active 2, maxActive 100, creating 1, createElapseMillis 26952, createErrorCount 66 ****

DTS-RETRY-ERR-0216: OutOfMemoryError

Possible cause: The length of a field in the task has reached the upper limit. As a result, an OOM error occurs.

Solution: Contact Alibaba Cloud technical support.

java.lang.OutOfMemoryError: Requested array size exceeds VM limit ****

DTS-RETRY-ERR-0222: execute statement failed

Possible cause: An error occurs when data is written to the destination database. This error occurs when an invalid time or date is written to the destination database that is an AnalyticDB for MySQL cluster.

Solution: Remove the table mentioned in the error message from the objects to be synchronized and add the table to the objects to be synchronized again. For more information, see What do I do if an error is reported for a table in a data synchronization instance? If the error persists, contact Alibaba Cloud technical support.

transaction-replicate: DTS-70004: execute statement failed: /* DTS-wri-MysqlEngine(3) */replace into `db_mch_recreation`.`tbl_order` (`time_pay`,`rec_product_detail`,`err_code`,`type`,`device_name`,`total_fee`,`out_sid`,`extra`,`ship_desc`,`sn`,`seller_id`,`time_create`,`device_id`,`err_desc

DTS-RETRY-ERR-0225: DTS-11005: null

Possible cause: An occasional error occurs.

Solution: Restart the task. If the error persists, contact Alibaba Cloud technical support.

framework: DTS-31009: In process of processing data (recordRange: ) failed cause: CriticalAnyAllException: common: DTS-11005: null NullPointerException: null [URL]: ****

DTS-RETRY-ERR-0226: User (.*)? does not have permission to run DBCC TRACEON

Possible cause: The database account that is used to access the source database does not have the required permissions.

Solution: Grant the sysadmin permissions to the database account and restart the task. For more information, see CREATE USER (Transact-SQL).

jobId=juin1gx7166****, code=15, errMsg=dts-k-src: DTS-52102: retry final failedcause:    RecoverableAnyAllException: dts-k-src: DTS-52110: SQLServerRecordExtractor Init Error: sqlserver-reader: DTS-00032: Execute sql DBCC TRACEON(2537,-1) failed, case by User 'dtstest' does not have permission to run DBCC TRACEON.    CriticalAnyAllException: sqlserver-reader: DTS-00032: Execute sql DBCC TRACEON(2537,-1) failed, case by User 'dtstest' does not have permission to run DBCC TRACEON.    SQLServerException: User 'dtstest' does not have permission to run DBCC TRACEON.

DTS-RETRY-ERR-0227: Socket closed

Possible cause: DTS cannot connect to the Redis instance.

Solution: Make sure that the networks of the source and destination databases are normal. Then, restart the task.

jobId=z6xb1321161****, code=04, errMsg=framework: DTS-31009: In process of processing data (recordRange: 444887303382577****) failedcause:    FatalAnyAllException: common: DTS-100047: retry 0 times, 15352498 seconds, which exceed the supposed 600 seconds    RedisServerException: redis: DTS-10015: redis: DTS-10009: Socket closed    RedisCannotRetryException: redis: DTS-10009: Socket closed    SocketException: Socket closed

DTS-RETRY-ERR-0228: Illegal mix of collations

Possible cause: The character sets or the collations for character sets in the source and destination databases are inconsistent.

jobId=yr6a1h2d161****, code=02, errMsg=Illegal mix of collations (utf8mb4_general_ci,IMPLICIT) and (utf8mb4_0900_ai_ci,IMPLICIT) for operation 'find_in_set'. Illegal mix of collations (utf8mb4_0900_ai_ci,IMPLICIT) and (utf8mb4_general_ci,IMPLICIT) for operation '='. Illegal mix of collations (utf8mb4_0900_ai_ci,IMPLICIT) and (utf8mb4_general_ci,IMPLICIT) for operation '='. Illegal mix of collations (utf8mb4_0900_ai_ci,IMPLICIT) and (utf8mb4_general_ci,IMPLICIT) for operation '='. Unknown column 'hjmall_jushuitan_brand_express_template.express_company' in 'on clause'. Illegal mix of collations (utf8mb4_0900_ai_ci,IMPLICIT) and (utf8mb4_general_ci,IMPLICIT) for operation '='. Illegal mix of collations (utf8mb4_0900_ai_ci,IMPLICIT) and (utf8mb4_general_ci,IMPLICIT) for operation '='. Illegal mix of collations (utf8mb4_0900_ai_ci,IMPLICIT) and (utf8mb4_general_ci,IMPLICIT) for operation '='. Unknown column 'b.excel_name' in 'field list'(advice: the base table may have been modified, you can choose to skip the migration of this View.).

DTS-RETRY-ERR-0232: cannot execute INSERT in a read-only transaction

Possible cause: The destination database is a read-only database.

jobId=f6au9q6b13c****, code=07, errMsg=transaction-replicate: DTS-70004: execute statement failed: /*f6au9q6b13cg9*****/insert into oms_ord.om_order_line (order_line_id,order_line_nbr,sale_channel,channel_order_nbr,order_time,order_id,cust_id,cust_name,order_type,pre_sale_date,delivery_method,pickup_point_code,contact_man,contact_num,contact_email,delivery_addr_id,delivery_detail_addr,expect_date,expect_time,cust_notes,if_remaining_paid,state,state_reason,state_date,state_desc,created_date,update_date,audit_notes,order_fulfill_id,order_fulfill_nbr,ship_date,order_fulfill_state,prod_desc,logistics_code,warehouse_id,warehouse_name,v_warehouse_id,v_warehouse_name,is_transfer,order_id_nbr,deliver_order_nbr,devy_longitude,devy_latitude,vmi_vendor_id,redo_count,currency_id,delivery_addr_l1,delivery_addr_l2,delivery_addr_l3,delivery_addr_l4,delivery_addr_zipcode,pay_state,delivery_state,delivery_chl_addr,if_oms_fulfill,payment_method,payment_time,region_code,ext_info,channel_type_id,ext_erp_order_nbr,ext_erp_delv_nbr,schedule_result_id,order_schedule_id,inv_chl_group_id,package_id) values(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)cause:    PSQLException: ERROR: cannot execute INSERT in a read-only transaction

DTS-RETRY-ERR-0234: DTS-70007: resolve failed

Possible cause: The topic does not exist in the destination Kafka cluster.

Solution: Create a topic in the Kafka cluster and restart the task. For more information about how to create a topic in an ApsaraMQ for Kafka instance, see the Step 1: Create a topic section of the "Step 3: Create resources" topic.

jobId=a4ls1hua154****, code=07, errMsg=framework: DTS-31009: In process of processing data (recordRange: 609533659628489****) failedcause:    FatalAnyAllException: common: DTS-100047: retry 0 times, 300800 seconds, which exceed the supposed 43200 seconds    CriticalAnyAllException: nosql-replicate: DTS-70007: resolve failed

DTS-RETRY-ERR-0235: permission denied to create event trigger

Possible cause: The database account that is used to access the destination database does not have the required permissions.

Solution: Reconfigure the task by using a superuser to access the destination database.

jobId=ipix1o7u13u****, code=30, errMsg=ERROR: permission denied to create event trigger "dts_intercept_ddl"  Hint: Must be superuser to create an event trigger.permission denied to create event trigger

DTS-RETRY-ERR-0236: Failed connecting to

Possible cause: DTS cannot connect to the Redis instance.

Solution: Make sure that the Redis instance can be connected and restart the task. If the error persists, contact Alibaba Cloud technical support.

jobId=v41u74p8z4q****, code=07, errMsg=framework: DTS-31007: fetch and merge schemas failedcause:    RedisServerException: redis: DTS-10015: redis: DTS-10010: Failed connecting to 100.115.XX.XX:XXX    RedisClientInitiationException: redis: DTS-10010: Failed connecting to 100.115.XX.XX:XXX

DTS-RETRY-ERR-0238: fetch log failed

Possible cause: An error occurs when DTS queries logs.

Solution: Contact Alibaba Cloud technical support.

jobId=q5lk1uak16g****, code=15, errMsg=dts-k-src: DTS-52111: Increment Context Is Not Running..: mysql-reader: DTS-52210: fetch log failedcause:    IOException: java.lang.ArrayIndexOutOfBoundsException: 6    ArrayIndexOutOfBoundsException: 6cause:    CriticalAnyAllException: mysql-reader: DTS-52210: fetch log failed    IOException: java.lang.ArrayIndexOutOfBoundsException: 6    ArrayIndexOutOfBoundsException: 6    fetch log failed

DTS-RETRY-ERR-0239: Prematurely reached end of stream

Possible cause: A timeout error occurs when DTS reads data from the source database.

Solution: Remove the timeout limit on the database on the premise that your business is not affected. If the error persists, contact Alibaba Cloud technical support.

jobId=mc9g16xe16d****, code=03, errMsg=framework: DTS-31009: In process of processing data (recordRange: 859496203590356****) failedcause:    FatalAnyAllException: common: DTS-100047: retry 0 times, 66950 seconds, which exceed the supposed 43200 seconds    RuntimeException: com.mongodb.MongoSocketReadException: Prematurely reached end of stream    MongoSocketReadException: Prematurely reached end of stream    Prematurely reached end of stream

DTS-RETRY-ERR-0240: Can not read response from server

Possible cause: DTS cannot obtain the data returned by the server.

Solution: Make sure that the network connection is normal, and restart the task. If the error persists, contact Alibaba Cloud technical support.

jobId=v72o16zi165****, code=03, errMsg=framework: DTS-31009: In process of processing data (recordRange: 71735997624221****) failedcause:    FatalAnyAllException: common: DTS-100047: retry 0 times, 2181031 seconds, which exceed the supposed 600 seconds    CriticalAnyAllException: framework: DTS-31009: read source data error    SQLException: Error retrieving record: Unexpected Exception: java.io.EOFException message given: Can not read response from server. Expected to read 11,302 bytes, read 6,941 bytes before connection was unexpectedly lost. ****

DTS-RETRY-ERR-0241: Unknown character set

Possible cause: The destination database does not support the character set mentioned in the error message.

Solution: To ensure compatibility, we recommend that the versions of the source and destination databases be the same or the version of the source database be earlier than that of the destination database.

jobId=n01d11o816q****, code=02, errMsg=Unknown character set: 'latin1'. Unknown character set

DTS-RETRY-ERR-0242: Could not find first log file name in binary log index file

Possible cause: The index information of the binary logs is not updated, and the binary logs are cleared.

Solution: Restore the binary logs or reconfigure the DTS task.

jobId=ud3m8u32154****, code=15, errMsg=dts-k-src: DTS-52102: retry final failedcause:    RecoverableAnyAllException: dts-k-src: DTS-52110: MySQLRecordExtractor Init Error: mysql-reader: DTS-52212: MySQL binlog 167384**** is not exists.    CriticalAnyAllException: mysql-reader: DTS-52212: MySQL binlog 167384**** is not exists.    IOException: java.sql.SQLException: Could not find first log file name in binary log index file    SQLException: Could not find first log file name in binary log index file

DTS-RETRY-ERR-0243: Record Convert error in table

Possible cause: The type of data to be written to the destination database is different from the data type defined in the schema.

Solution: Modify the schema of the table in the destination database to be the same as that in the source database. Then, restart the task.

jobId=el2m7hna195****, code=07, errMsg=DTS-077400: Record Convert error in table midea_database.midea_mmds_share_link_visit_log msg=[{column:object_id, value:6ba977b23944f68bf7124946aa3f****} To BIGINT]. cause by [{column:object_id, value:6ba977b23944f68bf7124946aa3f****} To BIGINT]    Record Convert error in table

DTS-RETRY-ERR-0245: Authentication failed

Possible cause: DTS cannot access the authentication database of the MongoDB instance.

Solution: Check whether the database account and password that are used by the task can connect to the database.

jobId=qbrn8mcj21p****, code=15, errMsg=dts-k-src: DTS-52102: retry final failedcause:    MongoSecurityException: Exception authenticating MongoCredential{mechanism=SCRAM-SHA-256, userName='dba_rw', source='admin', password=<hidden>, mechanismProperties={}}    MongoCommandException: Command failed with error 18 (AuthenticationFailed): 'Authentication failed.' on server 172.19.XX.XX:XXX. The full response is {"ok": 0.0, "errmsg": "Authentication failed.", "code": 18, "codeName": "AuthenticationFailed", "$clusterTime": {"clusterTime": {"$timestamp": {"t": 1673836841, "i": 41}}, "signature": {"hash": {"$binary": "gwps88TJItDHfP+xz0VQlY+****=", "$type": "00"}, "keyId": {"$numberLong": "715470944398737****"}}}, "operationTime": {"$timestamp": {"t": 1673836841, "i": 40}}}    Authentication failed

DTS-RETRY-ERR-0246: run check job timeout

Possible cause: The startup of a data verification task times out.

Solution: Contact Alibaba Cloud technical support.

jobId=q6rh1hi510o****, code=05, errMsg=run check job timeout

DTS-RETRY-ERR-0247: cannot execute DELETE in a read-only transaction

Possible cause: The DELETE operation is performed on a read-only node.

Solution: Restart the task. If the error persists, contact Alibaba Cloud technical support.

jobId=amjm8zwvc4h****, code=07, errMsg=DTS-077100: Record Replicator error in table dataintegration.dws_kmzk_stock_info. cause by [org.postgresql.util.PSQLException: ERROR: cannot execute DELETE in a read-only transaction] About more information in ****  cannot execute DELETE in a read-only transaction 

DTS-RETRY-ERR-0248: Socket read timed out

Possible cause: A timeout error occurs when DTS reads data from the source database.

Solution: Make sure that DTS can connect to the source database and restart the task.

id=38240****, jobId=vd6e8ylpa42****, value={"errMsg":"IO Error: Socket read timed out@error code:17002","jobId":"qs8x8nf815l****","maxRetryTime":7200,"module":"reader","retryCount":3,"retryTarget":"srcDB","retryTime":66,"retrying":true}

DTS-RETRY-ERR-0249: Version has changed

Possible cause: The object on which the SQL statement that is executed in the destination database depends does not exist. The object can be a function or the function on which a trigger depends.

Solution: Make sure that the destination database contains the objects on which the SQL statement depends.

jobId=kp0e16ge168****, value={"errMsg":"transaction-replicate: DTS-70004: execute statement failed: /*we2s1q2p16xc*****/update public.reconciliation set id = ?,create_time = ?,last_update = ?,data = ?,version = ? where id = ? \ncause:\n\tPSQLException: ERROR: Version has changed\n  Where: PL/pgSQL function update_version() line 8 at RAISE","jobId":"we2s1q2p16x****","maxRetryTime":43200,"module":"writer","retryCount":311,"retryTarget":"destDB","retryTime":3316,"retrying":true}  Version has changed

DTS-RETRY-ERR-0250: invalid identifier

Possible cause: The SQL statement fails to be executed in the destination database.

id=38235****, jobId=thvd19f2136****, value={"errMsg":"transaction-replicate: DTS-70004: execute statement failed: /*ewjw1e6a13mc9stOraclePrepareStatementSqlEngine(10)*/insert into \"SNPCENTER\".\"BIND\"(\"id\", \"sn\", \"snapshot_id\", \"parent_sn\", \"created_at\", \"updated_at\", \"parent_sn_from\", \"sn_from\") values(?, ?, ?, ?, ?, ?, ?, ?)\ncause:\n\tSQLSyntaxErrorException: ORA-00904: \"ID\": invalid identifier\n","jobId":"ewjw1e6a13m****","maxRetryTime":43200,"module":"writer","retryCount":421,"retryTarget":"destDB","retryTime":4315,"retrying":true}

DTS-RETRY-ERR-0251: unsupported value convert for

Possible cause: The type of data to be written to the destination database is different from the data type defined in the schema.

Solution: Modify the schema of the table in the destination database to be the same as that in the source database. Then, restart the task.

id=38235****, jobId=a4410xe0123****, value={"errMsg":"jdbc-utils: DTS-11001: jdbc-utils: DTS-11001: Adb30StringDisperse: unsupported value convert for [****] convert to [chief_account JSON nullable as chief_account] targetDatabase:hdd_prod_1 targetTable:basic_dock_account\ncause:\n\tJdbcUtilsException: jdbc-utils: DTS-11001: Adb30StringDisperse: unsupported value convert for [****] convert to [chief_account JSON nullable as chief_account]","jobId":"vgn10ctk19o****","maxRetryTime":7200,"module":"writer","retryCount":114,"retryTarget":"destDB","retryTime":1142,"retrying":true}

DTS-RETRY-ERR-0253: The network connection is not available, Please check the network connection of the source database and the target database

Possible cause: The network connection fails.

Solution: Make sure that the status of the source database is normal and the source database can be connected. Then, restart the task. If the error persists, contact Alibaba Cloud technical support.

The network connection is not available, Please check the network connection of the source database and the target database

DTS-RETRY-ERR-0254: Failed to connect to the database (.*)?

Possible cause: DTS fails to connect to the source database.

Solution: Make sure that the source database can be connected and restart the task.

jobId=ce7v1agz31w****, errMsg=Failed to connect to the database [S124.221.XX.XX:XXX].

DTS-RETRY-ERR-0255: NOSCRIPT No matching script

Possible cause: After a Lua script of the source database is mapped to the destination database, the keys of the Lua script are not allocated in the same hash slot in the destination database.

Solution: Modify the Lua script to make sure that the keys are allocated in the same hash slot in the destination database. Then, restart the task. If the error persists, contact Alibaba Cloud technical support.

jobId=envr2tt1x3b****, errMsg=redis.clients.jedis.exceptions.JedisNoScriptException: NOSCRIPT No matching script. Please use EVAL.

DTS-RETRY-ERR-0256: dayOfMonth must be in the range

Possible cause: The data to be written includes invalid data, such as invalid date and time data. As a result, the data fails to be written to the destination database.

Solution: Modify the schema of the table in the destination database to be the same as that in the source database. Then, restart the task.

**** 
2023-02-03 18:23:37 [sink-22] ERROR Adb30ReplicateSink: 269 - 22 execute batch dml failed cause [15018, 20230203182337192168132064031516924991] Cannot parse "2023-02-00 06:08:11.0": Value 0 for dayOfMonth must be in the range [1,28]java.sql.SQLException: [15018, 2023020318233719216813206403151692491] Cannot parse "2023-02-00 06:08:11.0": Value 0 for dayOfMonth must be in the range [1,28]

DTS-RETRY-ERR-0257: Invalid JSON text in argument 1 to function cast_as_json

Possible cause: The JSON field mentioned in the error message is empty and cannot be written to the destination database.

****  `project_description` = x'E6B58BE8AF95E9A1B9E79BAE303731****',`school_id` = 2632,`project_id` = 1,`group_id` = 36,`is_use` = 1 WHERE `project_id` = 1 limit 1, error detail message:Data truncation: Invalid JSON text in argument 1 to function cast_as_json: "The document is empty." at position 0.     MysqlDataTruncation: Data truncation: Invalid JSON text in argument 1 to function cast_as_json: "The document is empty." at position 0.

DTS-RETRY-ERR-0258: failed to parse date field

Possible cause: The format of the date field is invalid in the destination Elasticsearch cluster. As a result, the data fails to be written to the destination database.

Solution: Modify the format of the date field in the destination Elasticsearch cluster based on the source data and error message. Then, restart the task.

****
error detail message:es: DTS-10035: failed to parse field [mark_high_quality_label_time] of type [date] in document with id '30020'. Preview of field's value: '2023-02-03 17:40:27.0', failed to parse date field [2023-02-03 17:40:27.0] with format [strict_date_optional_time||epoch_millis]SQLException errorCode:0, record is: 
****

DTS-RETRY-ERR-0259: User (.*)? has exceeded the 'max_user_connections' resource

Possible cause: The number of database connections has reached the upper limit that is specified by the max_user_connections parameter.

Solution: Increase the maximum number of connections to the database and restart the task. For more information about how to modify the parameters of an ApsaraDB RDS for MySQL instance, see What do I do if the "has more than 'max_user_connections'" or "has exceeded the 'max_user_connections'" error message is displayed when I connect to an ApsaraDB RDS for MySQL instance?

jobId=v7yw20eea18****, errMsg=com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: User 'rrc_datax' has exceeded the 'max_user_connections' resource (current value: 50)

DTS-RETRY-ERR-0260: Failed For Wait Mysql Server Handshake

Possible cause: The database cannot be connected.

Solution: Make sure that the database can be connected and restart the task. If the error persists, contact Alibaba Cloud technical support.

jobId=r54w1gex11x****, errMsg=Increment Context Is Not Running..: com.alibaba.dts.exception.message.LocalException: DTS-002010 Unknow connect db 100.100.66.1:12703 failure. Original error: Failed For Wait Mysql Server Handshake, please check the health of db For more information please refer to https://****

DTS-RETRY-ERR-0261: UNSupport sqlserver without database backup

Possible cause: The database backup feature is not enabled for the self-managed SQL Server database.

Solution: Enable the database backup feature for the self-managed SQL Server database and restart the task. For more information, see the Preparations section of the "Synchronize data from a self-managed SQL Server database to an AnalyticDB for PostgreSQL instance" topic.

jobId=ibeh15uc28l****, errMsg=DTS-52102: retry final failed cause:     RecoverableAnyAllException: dts-k-src: DTS-52110: SQLServerRecordExtractor Init Error: sqlserver-reader: DTS-52402: UNSupport sqlserver without database backup     CriticalAnyAllException: sqlserver-reader: DTS-52402: UNSupport sqlserver without database backup

DTS-RETRY-ERR-0262: command 'SCRIPT' is not allowed

Possible cause: DTS does not allow you to synchronize or migrate scripts from a Redis instance.

Solution: Make sure that the source Redis instance does not contain scripts, and restart the task. If the error persists, contact Alibaba Cloud technical support.

jobId=mn9e254ps3r****,errMsg=redis.clients.jedis.exceptions.JedisDataException: ERR handle request, command 'SCRIPT' is not allowed

DTS-RETRY-ERR-0263: UnsupportedException (.*)? Cannot support Version

Possible cause: DTS does not support Redis 7.0 or later.

Solution: None.

jobId=hp9m2axpv47****,errMsg=DTS-31009: In process of processing data (recordRange: 27873049260****) failed cause:     FatalAnyAllException: common: DTS-100047: retry 0 times, 1601 seconds, which exceed the supposed 43200 seconds     RedisServerException: redis: DTS-10015: redis: DTS-11005: Cannot support Version: 10     UnsupportedException: redis: DTS-11005: Cannot support Version: 10

DTS-RETRY-ERR-0264: TDDL-4500 (.*)? Do not support partition by

Possible cause: The PolarDB-X database in DRDS mode does not support automatic partitioning.

jobId=c78q2olvv3c****, errMsg=[15a0362958404000][11.117.XXX.XXX:3088][jm_live_data_pool]ERR-CODE: [TDDL-4500][ERR_PARSER] Do not support partition by. . 

DTS-RETRY-ERR-0265: Rejecting mapping update to

Possible cause: The index that you want to create already exists in the destination database of the DTS task.

Solution: Delete the index from the destination database on the premise that your business is not affected. Then, restart the task.

jobId=hvfm2r55y36****, errMsg=PUT http://172.17.XX.XX:XXX/equity_request_log/_mapping/equity_request_log_1?include_type_name=true&pretty=true: HTTP/1.1 400 Bad Request {   "error" : {     "root_cause" : [       {         "type" : "illegal_argument_exception",         "reason" : "Rejecting mapping update to [equity_request_log] as the final mapping would have more than 1 type: [_doc, equity_request_log_1]"       }     ],     "type" : "illegal_argument_exception",     "reason" : "Rejecting mapping update to [equity_request_log] as the final mapping would have more than 1 type: [_doc, equity_request_log_1]"   },   "status" : 400 } . PUT http://172.17.XX.XX:XXX/equity_request_log/_mapping/equity_request_log_10?include_type_name=true&pretty=true: HTTP/1.1 400 Bad Request {   "error" : {     "root_cause" : [       {         "type" : "illegal_argument_exception",         "reason" : "Rejecting mapping update to [equity_request_log] as the final mapping would have more than 1 type: [_doc, equity_request_log_10]"       }     ],     "type" : "illegal_argument_exception",     "reason" : "Rejecting mapping update to [equity_request_log] as the final mapping would have more than 1 type: [_doc, equity_request_log_10]"   },   "status" : 400 }

DTS-RETRY-ERR-0266: Unknown collation

Possible cause: The destination database does not support the encoding formats of tables in the source database.

jobId=eb6o2xm5e3o****, errMsg=Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'. Unknown collation: 'utf8mb4_0900_ai_ci'.

DTS-RETRY-ERR-0267: Invalid column name (.*)?

Possible cause: The column mentioned in the error message does not exist in the destination database. As a result, an object that depends on the column cannot be created.

Solution: Check the validity of the column. If the column is invalid, ignore the column and restart the task. If the error persists, contact Alibaba Cloud technical support.

jobId=ofyn25r1t4b****, errMsg=Invalid column name 'TotalAmount'. Invalid column name 'wx_flag'. . 

DTS-RETRY-ERR-0268: Invalid object name (.*)?

Possible cause: The object on which the current task depends is invalid.

jobId=dcpd2mm3p3f****, errMsg=Invalid object name 'dbo.V_BS_INFO'. Invalid object name 'dbo.V_BS_INFO'. Invalid object name 'V_BS_INFO'. Invalid object name 'V_BS_INFO'. Invalid object name 'V_CGO_CN_PRE'. . 

DTS-RETRY-ERR-0269: Error column name

Possible cause: The destination database does not support the encoding format of the synchronized or migrated object mentioned in the error message.

Solution: Make sure that the encoding formats of the synchronized or migrated objects are supported in the destination database based on the error message. Then, restart the task.

jobId=t6ds676q308****, errMsg=DTS-1029999 The ddlmove task t6ds676q308**** was finished,but 1 objects failed,error message:DTS-1020042 Execute sql error sql: DTS-1020042 Execute sql error sql: [13000, 202006301129351720160291070345367****] Error column name: 'id',only support '0-9,a-z,A-Z,_-()' and first letter must be a-z or 

DTS-RETRY-ERR-0270: MongoCommandException (.*)? operation was interrupted

Possible cause: A timeout error occurs when indexes are created for a MongoDB database.

Solution: Restart the task. If the error persists, increase the timeout period for DDL statements executed in the MongoDB database and restart the task.

jobId=b0tm16z731k****, errMsg=com.mongodb.MongoCommandException: Command failed with error 11602: 'operation was interrupted' on server 172.17.XX.XX:XXX. The full response is { "writeConcernError" : { "code" : 11602, "codeName" : "InterruptedDueToReplStateChange", "errmsg" : "operation was interrupted" }, "operationTime" : { "$timestamp" : { "t" : 1675441117, "i" : 2682 } }, "ok" : 0.0, "errmsg" : "operation was interrupted", "code" : 11602, "codeName" : "InterruptedDueToReplStateChange", "$clusterTime" : { "clusterTime" : { "$timestamp" : { "t" : 1675441145, "i" : 65 } }, "signature" : { "hash" : { "$binary" : "HKKlWcyFaBhMJYL5Fk9kGlpIyCU=", "$type" : "00" }, "keyId" : { "$numberLong" : "716938648110917****" } } } }. com.mongodb.MongoCommandException: Command failed with error 11602: 'operation was interrupted' on server 172.17.XX.XX:XXX. The full response is { "writeConcernError" : { "code" : 11602, "codeName" : "InterruptedDueToReplStateChange", "errmsg" : "operation was interrupted" }, "operationTime" : { "$timestamp" : { "t" : 1675441117, "i" : 2667 } }, "ok" : 0.0, "errmsg" : "operation was interrupted", "code" : 11602, "codeName" : "InterruptedDueToReplStateChange", "$clusterTime" : { "clusterTime" : { "$timestamp" : { "t" : 1675441145, "i" : 65 } }, "signature" : { "hash" : { "$binary" : "HKKlWcyFaBhMJYL5Fk9kGlpIyCU=", "$type" : "00" }, "keyId" : { "$numberLong" : "716938648110917****" } } } }.

DTS-RETRY-ERR-0271: fullcheck find different records

Possible cause: The data verification task detects inconsistent data.

**** fullcheck find different records : 9

DTS-RETRY-ERR-0272: UnSupport this db type

Possible cause: The current task does not support the ETL feature.

Solution: Remove the configurations of the ETL feature from the task.

jobId=uqct2lfuv57****, errMsg=java.lang.Exception: UnSupport this db type : 131072
  at ****

DTS-RETRY-ERR-0273: Deadlock found when trying to get lock

Possible cause: Another user is writing data to the destination database. As a result, a deadlock occurs when DTS writes data to the destination database for the current task.

Solution: Stop other write operations on the destination database on the premise that your business is not affected and try again. If the error persists, contact Alibaba Cloud technical support.

jobId=x1sz2los149****, errMsg=framework: DTS-30011: currentRunningSQL: /* DTS-full-x1sz2los149**** */insert ignore into **** , reason: Deadlock found when trying to get lock; try restarting transactioncause:    BatchUpdateException: Deadlock found when trying to get lock; try restarting transaction    MySQLTransactionRollbackException: Deadlock found when trying to get lock; try restarting transaction

DTS-RETRY-ERR-0274: Tablespace has been discarded for table

Possible cause: DTS fails to read data from the source database.

Solution: Make sure that the table for which the error is reported in the source database can be read. Then, restart the task.

jobId=yd0b2c2a148****, errMsg=framework: DTS-31009: In process of processing data (recordRange: 381808368541709****) failedcause:    FatalAnyAllException: common: DTS-100047: retry 712 times, 7205110 seconds, which exceed the supposed 7200 seconds    CriticalAnyAllException: framework: DTS-31009: read source data error    SQLException: Tablespace has been discarded for table 'dtstest'

DTS-RETRY-ERR-0275: is not nullable (.*)? but it's default value is null

Possible cause: A null value is written to a column that has the NOT NULL constraint in the destination database.

Solution: Remove the NOT NULL constraint from the columns mentioned in the error message in the destination table on the premise that your business is not affected. Then, restart the task.

jobId=lg7d2ofq14v****, errMsg=common: DTS-100047: retry 4310 times, 43202322 seconds, which exceed the supposed 43200 secondscause:    RuntimeException: Table '`dw`.`f_fa_fnd_repay_recon`' with columns [****] and batch exception is {[13000, 202302150420401921681740920315141****] F_FA_FND_REPAY_RECON.BANK is not nullable, but it's default value is null, Error : Field 'F_FA_FND_REPAY_RECON.BANK' doesn't have a default value}    BatchUpdateException: [13000, 202302150420401921681740920315141****] F_FA_FND_REPAY_RECON.BANK is not nullable, but it's default value is null, Error : Field 'F_FA_FND_REPAY_RECON.BANK' doesn't have a default value    MySQLSyntaxErrorException: [13000, 202302150420401921681740920315141****] F_FA_FND_REPAY_RECON.BANK is not nullable, but it's default value is null, Error : Field 'F_FA_FND_REPAY_RECON.BANK' doesn't have a default value

DTS-RETRY-ERR-0276: if (.*)? is specified it must not be empty

Possible cause: The value mapped to the_id column in the destination Elasticsearch cluster is empty.

Solution: Reconfigure the task and configure filter conditions when you select the objects to be synchronized or migrated to filter out data whose value is an empty string. For more information, see Use SQL conditions to filter data.

jobId=usbt2jev15uw11k, errMsg=common: DTS-100047: retry 15 times, 265289 seconds, which exceed the supposed 9223372036854775807 secondscause:    IOException: es: DTS-10035: if _id is specified it must not be empty    CriticalAnyAllException: es: DTS-10035: if _id is specified it must not be empty

DTS-RETRY-ERR-0277: The primary key schema is not match which defined in table meta

Possible cause: The primary key of a table is inconsistent with the schema information obtained by DTS.

Solution: Create another task. If the error persists, contact Alibaba Cloud technical support.

jobId=j4qs239715r****, errMsg=common: DTS-100047: retry 0 times, 2056 seconds, which exceed the supposed 43200 secondscause:    ClientException: The primary key schema is not match which defined in table meta.

DTS-RETRY-ERR-0278: Unexpected end of stream

Possible cause: An error occurs when DTS connects to a database instance.

Solution: Check the network information such as the whitelist to make sure that the database can be connected. Then, restart the task. For more information, see Source database connectivity and Destination database connectivity.

jobId=ofmz2m6015t****, errMsg=framework: DTS-31007: fetch and merge schemas failedcause:    RedisServerException: redis: DTS-10015: redis: DTS-10010: Unexpected end of stream.    RedisClientInitiationException: redis: DTS-10010: Unexpected end of stream.

DTS-RETRY-ERR-0279: Unsupport batch replicate in kafka

Possible cause: The current task does not support the batch writing feature. You must disable the feature.

Solution: Contact Alibaba Cloud technical support.

jobId=f3uc324ha1c****, errMsg=kafka: DTS-31005: Unsupport batch replicate in kafka

DTS-RETRY-ERR-0280: Could not get a resource since the pool is exhausted

Possible cause: DTS cannot connect to the Redis instance.

Solution: Make sure that DTS can connect to the source or destination Redis instance, and restart the task.

jobId=sjcg2si2141****, errMsg=redis: DTS-10015: Could not get a resource since the pool is exhaustedcause:    JedisExhaustedPoolException: Could not get a resource since the pool is exhausted    NoSuchElementException: Unable to validate object

DTS-RETRY-ERR-0281: RDB Magic String Error

Possible cause: DTS does not support a Redis instance of the current version. As a result, DTS fails to parse data of the Redis instance.

Solution: Use a Redis instance of a version that is supported by DTS and try again. If the error persists, contact Alibaba Cloud technical support.

jobId=rs1r2ub614****, errMsg=framework: DTS-31009: In process of processing data (recordRange: 2093173747887374336) failedcause:    FatalAnyAllException: common: DTS-100047: retry 0 times, 1501 seconds, which exceed the supposed 43200 seconds    RedisServerException: redis: DTS-10015: redis: DTS-10019: RDB Magic String Error: [84, 68, 69, 95, 69, 78, 65, 66, 76]    UnexpectedRDBFromatException: redis: DTS-10019: RDB Magic String Error: [84, 68, 69, 95, 69, 78, 65, 66, 76]

DTS-RETRY-ERR-0282: Can not create connection to source database

Possible cause: An error occurs when DTS connects to a database instance.

Solution: Check the network information such as the whitelist to make sure that the database can be connected. Then, restart the task. For more information, see Source database connectivity and Destination database connectivity.

jobId=sd4q2knu13t****, errMsg=dts-k-src: DTS-52111: Increment Context Is Not Running..: cause:    CriticalAnyAllException: sqlserver-reader: DTS-52410: Sqlserver log fetch failed    CriticalAnyAllException: sqlserver-reader: DTS--0001: Can not create connection to source database    SQLServerException:  ****

DTS-RETRY-ERR-0283: the password has expired

Possible cause: The account of the Oracle database expires. As a result, DTS cannot connect to the database.

Solution: Modify the database account to make sure that DTS can connect to the Oracle database by using this account. For example, change the account password.

jobId=h0vu2cqvb73****, errMsg=dts-k-src: DTS-52111: Increment Context Is Not Running..: cause:    CriticalAnyAllException: oracle-reader: DTS-52320: Fetch oracle log failed    CriticalAnyAllException: oracle-reader: DTS-52320: Fetch redo log failed    CriticalAnyAllException: oracle-reader: DTS--0001: Can not create connection to source database, case by ORA-28001: the password has expired    SQLException: ORA-28001: the password has expired

DTS-RETRY-ERR-0284: postgres create local slot failed

Possible cause: DTS fails to create a replication slot in the source database.

Solution: Execute the SELECT * FROM pg_stat_activity WHERE pid != pg_backend_pid() AND (now() - xact_start > INTERVAL '600s'); statement on the source database to check whether a long-running transaction stops DTS from creating a replication slot. If a long-running transaction exists, wait until the transaction ends and try again. If the error persists, contact Alibaba Cloud technical support.

jobId=hkdy2ysl13j****, errMsg=bisId [hl3o2c0n13r****] run fail by ****,errorMsg:reader m36f2x3115g**** start fail,current state failed , msg : dts-k-src: DTS-52111: Increment Context Is Not Running..: cause:    CriticalAnyAllException: postgresql--reader: DTS-52510: Fetch postgresql logical log failed CriticalAnyAllException: postgresql-reader: DTS-52513: postgres create local slot failed

DTS-RETRY-ERR-0285: Error In Parsing RDB

Possible cause: The database account that is used by the DTS task does not have the required permissions on the Redis database.

Solution: Check whether the account of the Redis database has the required permissions based on the relevant documentation. If the account does not have the required permissions, grant the required permissions to the account and try again. If the account has the required permissions, contact Alibaba Cloud technical support.

jobId=v5i12pl522s****, errMsg=framework: DTS-31009: In process of processing data (recordRange: 27873049260****) failedcause:    RedisServerException: redis: DTS-10015: redis: DTS-10019: Error In Parsing RDB, Format Error, First Line is :-ERR request failed to route, command 'sync' raw ****

DTS-RETRY-ERR-0286: You can't write or read against a disable instance

Possible cause: DTS cannot read data from or write data to the source database.

Solution: Make sure that data can be read from and written to the source database, and restart the task.

jobId=rp4r2jdc14y****, errMsg=framework: DTS-31007: fetch and merge schemas failedcause:    RuntimeException: sourceDB execute info Keyspace return unexpected error, response: null    JedisDataException: ERR DISABLE You can't write or read against a disable instance

Other common errors

DTS-10015

Problem description: A Redis database cannot be connected.

Possible cause: The Redis server cannot be connected because an exception has occurred.

Solution: Check the status of the Redis server and make sure that the server can be connected.

DTS-10015: unreachable redis network.JedisConnectionException: Could not get a resource from the poolJedisConnectionException: Failed connecting to ip_address:portConnectException: Connection timed out (Connection timed out)

DTS-10046

Problem description: An exception occurs when SQL statements are being executed.

Possible cause: The database account does not have the CREATE TABLE permission.

DTS-10046: execute sql: CREATE TABLE if not exists`dts`.`table_name` ( `id` int(11) NOTNULL,`column1` bigint(20) NOT NULL, PRIMARY KEY (`id`)) ENGINE=InnoDB DEFAULTCHARSET=utf8 failed. Create TransactionTable failed. cause:MySQLSyntaxErrorException: CREATE command denied to user 'username'@'ip_address' for table 'table_name'

DTS-30005

Problem description: Metadata cannot be saved during internal processing.

Possible cause: Two tables in the source database have the same name that differs only in capitalization, such as TABLE and table. DTS considers that the two table names conflict with each other.

Solution: Check the table names in the source database and rename one of the tables. Then, restart the task.

DTS-30005: save changed job progress info failed cause: SQLException:result content unexpected. expect 3 time 1, actually [2, 1, 1]

DTS-30011

Problem description: An exception occurs when data is being written.

DTS-30011:put 2048 records error, currentRunningSQL:insert ignore into `xxx`.`yyy`(...), currentRunningRecordRange:{id:5362875948821643265,xxx.yyy,field:DefaultRecordField:{fieldName=aaa, dataType={typeName:BIGINT, typeId:-5, isLobType:false,encoding:null}, sourceDataType=null, aliases=[], defaultValue=null,nullable=false, unique=true, primary=true,generated=false},leftValue:1293615822270500864,rightValue:1311217506282770432,partition:null}cause: BatchUpdateException: The table 'yyy' is full SQLException: The table'yyy' is full

Possible cause 2: A lock wait timeout occurs in the destination database.

SHOW FULL PROCESSLIST;
SELECT
* FROM innodb_trx;

DTS-30011: put 2048 records error, currentRunningSQL:insert ignore into`xxx`.`yyy`(...:{id:4958981218625388545,schema:xxx.yyy,field:DefaultRecordField:{fieldName=aaa, dataType={typeName:INTEGER, typeId:4, isLobType:false,encoding:null}, sourceDataType=null, aliases=[], defaultValue=null,nullable=false, unique=true, primary=true,generated=false},leftValue:512021,rightValue:1024022,partition:null} cause:BatchUpdateException: Lock wait timeout exceeded; try restarting transactionMySQLTransactionRollbackException: Lock wait timeout exceeded; try restartingtransaction

Possible cause 3: The destination database is in the read-only state.

DTS-30011: put 2048 records error, currentRunningSQL:insert ignore into`xxx`.`yyy`(`...,currentRunningRecordRange:{id:4050997257913237860,schema:xxx.yyy,field:DefaultRecordField:{fieldName=id, dataType={typeName:BIGINT, typeId:-5, isLobType:false, encoding:null},sourceDataType=null, aliases=[], defaultValue=null, nullable=false,unique=true, primary=true,generated=false},leftValue:5424204045,rightValue:5424982251,partition:null}cause: SQLException: The MySQL server is running with the --read-only option soit cannot execute this statement

DTS-30018

Problem description: The specified column does not exist.

DTS-30018: Can not find column [column_in_source<-->column_in_target] in target table db_name.table_name

DTS-30019

Problem description: The specified column does not exist.

DTS-30019: Can not find column [column_in_source<-->column_in_target] in target table db_name.table_name

DTS-30020

Problem description: An exception occurs when SQL statements are being executed.

Possible cause: The database account does not have the CREATE TABLE permission.

DTS-30020: execute sql: CREATE TABLE if not exists`dts`.`table_name` ( `id` int(11) NOTNULL,`column1` bigint(20) NOT NULL, PRIMARY KEY (`id`)) ENGINE=InnoDB DEFAULTCHARSET=utf8 failed. Create TransactionTable failed. cause:MySQLSyntaxErrorException: CREATE command denied to user 'username'@'ip_address' for table 'table_name'

DTS-31009/DTS-51009/DTS-50019

Problem description: The data write module cannot read data at the specified point in time from the data cache module.

Possible cause 2: The task failed for an extended period of time. After you fix the issue, the data cache module has no data at a specific consumption checkpoint.

Solution: Create another task. If an error occurs when the task is running, we recommend that you fix the error and resume the task at the earliest opportunity. A task that failed for an extended period of time may not be resumed as expected.

Possible cause 3: During full data migration or synchronization, DTS circularly stores data logs of the previous 24 hours or 50 GB of data logs for the source database. The stored data logs are used for incremental data parsing. If full data migration or synchronization lasts for an extended period of time, DTS may clear the data logs that are cached after the task is started. As a result, the data logs used for incremental data parsing are incomplete.

Solution 3: Create another task. Before you create the task, evaluate the amount of data to be migrated or synchronized. If the amount of data is large, we recommend that you create multiple tasks.

DTS-31009: In process of processing data (recordRange: 911705268553777****) failed cause: CriticalAnyAllException: 
capture-dstore: DTS-51009: Failed to fetch records from dstore CriticalAnyAllException: capture-dstore: DTS-50019: 
seek timestamp for topic [-0] with position [{"timestamp":1621516671, "offset":-1}] failed

DTS-31009/DTS-51009

Problem description: When the data write module reads data from the data cache module, a connection timeout occurs.

Possible cause: The connection between the data write module and the data cache module times out due to network jitters.

Solution: Restart the task and check whether the task can be resumed.

DTS-31009: In process of processing data (recordRange: 579980698763814****) failed cause: CriticalAnyAllException: 
capture-dstore: DTS-51009: Failed to fetch records from dstore TimeoutException: Failed to get offsets by times in 
120000 ms

DTS-60001

Problem description: The source database cannot be connected.

Possible cause: You enter an invalid username or password.

DTS-60001: Create connection failed (url:ip_address:port, user: username) cause: SQLException: Access denied for user'username'@'ip_address' (using password: YES)

DTS-61015

Problem description: The source database cannot be connected.

Possible cause: The number of connections to the source database has reached the upper limit.

DTS-61015: Create connection failed(url:ip_address:port, user: username) cause:MySQLNonTransientConnectionException: Data source rejected establishment ofconnection, message from server: "Too many connections"

DTS-70002

Problem description: A database cannot be connected, or the specified database or table does not exist.

Possible cause: An error occurs during schema migration. As a result, the specified table is not migrated to the destination database. In addition, you have not created a table in the destination database that has the same schema as the specified table.

DTS-70002: get table detail info failed after 151times (user: db_name, database:table_name) MySQLSyntaxErrorException: Table 'db_name.table_name'doesn't exist

DTS-70004

Possible cause 1: DTS does not support relevant DDL statements in data synchronization scenarios. As a result, the DDL statements fail to be executed.

DTS-70004: execute statement failed: /*dts_id=dtsaaaaaaaaaa*/alter table`xxx`.`yyy` modify column `aaa` INT default 0 comment 'bbb' cause:SQLException: [15018, 2021030506452201000000420803151947572] modify column type is not supported, col=x, oldType=bigint, newType=int

Possible cause 2: The SHUTDOWN operation is performed on the destination database.

Solution: Make sure that the destination database is running and restart the data synchronization task.

DTS-70004:execute statement failed: /*aaaaaaaaaaMysqlEngine(28)*/update `xxx`.`yyy` set... error detail message:Server shutdown in progress MySQLNonTransientConnectionException: Server shutdown in progress

Possible cause 3: The network is unavailable or the account does not have the required permissions. As a result, the AnalyticDB for MySQL database does not allow the account to perform remote logon.

DTS-70004:execute statement failed: /*aaaaaaaaaaMysqlEngine(27)*/update `xxx`.`yyy` set... cause: SQLException: null, message from server: "Host '192.10.XX.XX' isnot allowed to connect to this MySQL server"

Possible cause 4: The specified table does not exist.

DTS-70004: execute statement failed: /*bg6l15vf29l1b0vMysqlEngine(16)*/insertinto `xxx`.`yyy` ... error detail message:Table 'xxx.yyy' doesn't existMySQLSyntaxErrorException: Table 'xxx.yyy' doesn't exist

Possible cause 5: The integrity constraints of the database are violated. For example, NULL values are inserted into a NOT NULL column.

Solution: Check the table schemas and the data records involved in the DML statements. Make sure that the schemas of the source and destination tables are consistent or revise the data records. Then, restart the task.

DTS-70004: execute statement failed:/*o3z5bntMysqlEngine(0)*/insert into`xxx`.`yyy` ...error detail message:Column 'aaa' cannot be nullMySQLIntegrityConstraintViolationException: Column 'aaa' cannot be null

Possible cause 6: The account of the destination database does not have the required permissions.

Solution: Check whether the account of the destination database has the permissions mentioned in the error message. If not, grant the permissions to the account and restart the task.

DTS-70004: execute statement failed:/*s2gb356ds228bt8MysqlEngine(0)*/insert into `xxx`.`yyy` (`...`)values(...)error detail message:INSERT command denied to user'user'@'100.104.175.31' for table 'yyy' MySQLSyntaxErrorException: INSERTcommand denied to user 'user'@'100.104.175.31' for table 'yyy'

DTS-70019

Problem description: The specified column does not exist.

DTS-70019: Can not find column [column_in_source<-->column_in_target] in target table db_name.table_name

DTS-71016

Problem description: The destination database cannot be connected.

Possible cause 1: The number of connections to the destination database has reached the upper limit.

Solution: Increase the maximum number of connections to the destination database. Then, restart the task.

DTS-71016: connect target failed (url: jdbc:mysql://ip_address:port?parameters)cause: MySQLNonTransientConnectionException: Data source rejected establishmentof connection, message from server: "Too many connections"

Possible cause 2: An excessive number of failed database connections are generated by the same IP address in a short period of time. As a result, new connections are blocked.

Solution: Troubleshoot the error in the destination database. For example, increase the value of the MAX_CONNECTION_ERRORS parameter. Then, restart the task.

DTS-71016: connect target failed (url: jdbc:mysql://ip_address:port?parameters)cause: SQLException: null, message from server: "Host 'ip_address' isblocked because of many connection errors; unblock with 'mysqladminflush-hosts'"

DTS-1051009

Problem description: An exception occurs when DTS parses binary logs from a MySQL database.

Possible cause: The schemas stored in the binary logs of the MySQL database are inconsistent with the schemas stored in DTS. Schema inconsistency occurs if a DDL statement that changes the schema of a table is not recorded in the binary logs. As a result, DTS cannot parse the DDL statement and does not update the schema. For example, you execute the SET SESSION sql_log_bin=0 statement to change the field type of a table from INT(11) to BIGINT(20).

Solution: Update the schemas stored in DTS. Contact Alibaba Cloud technical support.

java.IOEException: java.lang.IllegalArgumentException: Valid type fail, Column:column_name,Type:type_number

DTS-100047

Problem description: The connection between DTS and a database instance times out.

Possible cause: Parameters related to the timeout period are set to small values for the database instance.

Solution: Increase the values of the net_read_timeout and net_write_timeout parameters and restart the task.

****
FatalAnyAllException:common:DTS-100047:retry0times,4791628seconds,whichexceedthesupposed600seconds
CriticalAnyAllException:framework:DTS-31009:readsourcedataerror
****