How to resolve error messages returned during task configuration and runtime-Data Transmission Service(DTS)-阿里云帮助中心

This topic describes common error messages that Data Transmission Service (DTS) returns during task configuration and runtime, such as retry information or error codes, and provides solutions.

Note

This topic uses regular expressions in the format (.*)? to represent variables in error messages.
If you cannot resolve an error, you can join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client) for assistance.

Error overview

Data Transmission Service (DTS) has the following four types of common errors:

Common errors during task configuration
Common errors during task runtime
Other common errors
Errors related to table schemas

Common errors during task configuration

DTS.Msg.LXCreateOrderError

Scenario: Order creation fails when you purchase a DTS instance.

Possible cause: Your UID is not on the allowlist, so you cannot purchase a cross-border synchronization instance.

Solution: Enable cross-border synchronization permissions and repurchase the instance. For more information, see Apply for cross-border data synchronization permissions.

DTS.Msg.InvalidParameter.KafkaHostInvalid

Scenario: You are configuring a Kafka synchronization or migration task where the connection type for the destination database instance is Leased Line, VPN Gateway, or Smart Gateway.

Possible cause: You entered a domain name instead of an IP address in the IP Address field.

Solution: The IP Address field supports only IPv4 addresses. Enter the correct private IP address.

DTS.Msg.InvalidParameter.KafkaBrokerInvalid

Scenario: You configure a Kafka task whose destination database is an ECS-hosted Kafka instance.

Possible cause: Kafka broker configurations do not support domain names.

Solution: Configure your Kafka brokers correctly. Use this format:

listeners= protocol://private_ip:port
advertised_listeners= protocol://private_ip:port

DTS.Msg.OperationDenied.JobStatusModifying

Scenario: You call the ModifyDtsJob API operation to modify a synchronization task.

Possible cause: The task's host instance is in the Modifying Synchronization Objects state.

Resolution: Wait until the modification is complete and the instance status is Running, then retry.

DTS.Msg.InvalidParameter.AliyunUidFormat

Scenario: You click Show Database Instances when configuring cross-account synchronization.

Possible cause: The Alibaba Cloud UID of the source database instance is incorrectly formatted.

Solution: Enter a valid Alibaba Cloud account.

DTS.Msg.DuplicateAccount.RDSSqlServer

Scenario: You configure a task whose source or destination database is SQL Server.

Possible cause: The instance is already configured with a DTS task or is a clone instance.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DTS.Msg.SrcLink.InternetAddressNotFound

Scenario: You configure a cross-region migration task.

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

Solution: Enable a public endpoint for the source database instance or use a synchronization task.

DTS.Msg.UpdateJob.OperationDenied.InitStatus

Scenario: You repeatedly configure a task.

Possible cause: You attempt to reconfigure a running synchronization task.

Solution: Reset the task or modify the synchronization objects.

Warning

Resetting the task clears all configured task data. Proceed with caution.

DTS.Msg.Throttling.User

Scenario: This error may occur when you use any DTS feature.

Possible cause: You have reached the request quota for the current API operation.

Solution: Retry the request after 15 to 30 seconds.

DTS.Msg.LXCreateOrder.NotFoundPricePlan

Scenario: Order creation fails when you purchase a DTS instance.

Possible cause: You entered incorrect purchase parameters in the API call or the instance type is temporarily unavailable.

Solution: Check that the specified parameters are correct, and then retry. If you confirm that the parameters are correct, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DTS.Msg.LXPayOrder.InsufficientBalance

Scenario: Payment fails when you purchase a DTS instance.

Possible cause: Your account balance is insufficient to complete the payment.

Solution: Recharge your account and retry.

DTS.Msg.CheckStatus.InvalidInitStatus

Scenario: You use the Modify Synchronization Objects feature.

Possible cause: The synchronization task is not yet configured.

Solution: Complete the task configuration before you modify synchronization objects.

DTS.Msg.DRDSInvokeFail.DatabaseAuthorizationFailed

Scenario: An error occurs when you configure a synchronization task for PolarDB-X (formerly DRDS). The error message resembles the following:

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 database account lacks permissions on one or more databases.

Solution: Manually add or modify database permissions by following these steps:

Log on to the PolarDB-X console.
In the left navigation pane, click Instances. Then click the Instance Name for the one you created.
On the instance management page, choose Configuration & Management > Account Management.
To add or modify database permissions, select the database account that you created and click Modify Permissions in the Actions column.
Click OK.

DTS.Msg.DescribeColumns.TimeOut

Scenario: Failed to retrieve column information from the source database. This commonly occurs for tasks whose destination database is AnalyticDB for MySQL.

Possible cause: The source database contains too many columns or reads slowly, which causes schema retrieval to time out.

Solution:

Configure the task using the API.
Verify the read speed of the source database.

DTS.Msg.DescribeStruct.TimeOut

Problem: The connection test succeeds, but you cannot retrieve tables from the source database.

Possible cause: The source database contains too many databases or tables, or reads slowly, which causes schema retrieval to time out.

Solution:

Configure source database objects at the database level without retrieving detailed table information.
Configure the task using the API.
Verify the read speed of the source database.

DTS.Msg.DRDSErrExecuteOnMySQL.ClientVersionTooLow

Scenario: You configure a task whose source database is PolarDB-X (formerly DRDS).

Possible cause: The PolarDB-X client version is outdated.

Solution: Upgrade the PolarDB-X client.

DTS.Msg.DbTypeNotSupport.OnlyReadRDS

Scenario: You configure a task whose source database is PolarDB-X (formerly DRDS).

Possible cause: The Database Type of the source database instance is Read-only Instance. DTS does not currently support this instance type.

Resolution: Change the source database to a PolarDB-X instance with a Database Type of Primary Instance.

DTS.Msg.DbTypeNotSupport.PolarDBRDS

Scenario: You configure a task whose source database is PolarDB-X (formerly DRDS).

Possible cause: The source database instance has a Storage Type of POLARDB. DTS does not currently support this instance type.

Resolution: Change the source database to a PolarDB-X instance where the Storage Type is RDS MySQL.

DTS.Msg.OperationDenied.NotPurchased

Scenario: Task startup fails when you call an API operation.

Possible cause: You try to start a task that you have not purchased.

Solution: Purchase the task before you start it.

DTS.Msg.CheckJobFailed.ServerUnAvailable

Scenario: An error occurs during task configuration.

Possible cause: DTS cannot connect to the server node where the task runs, so it cannot verify network connectivity between the server node and the source or destination database.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DTS.Msg.StopJobFailed.ServerUnAvailable

Scenario: An error occurs during task configuration.

Possible cause: DTS cannot connect to the server node where the task runs when it needs to pause the task.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DTS.Msg.SQLExecuteError.JDBC4CommunicationsException

Scenario: Schema retrieval fails after the test connection succeeds.

Possible cause: A communication link failure occurs. The JDBC driver successfully sends packets to the source database server but receives no response.

Solution:

Check whether the database connection limit is exceeded.
For troubleshooting information, see communications link failure.
For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DTS.Msg.SQLExecuteError.ConnectionRefused

Scenario: Schema retrieval fails after the test connection succeeds.

Possible cause: The connection to the source database is refused.

Solution:

Verify that the listener process is running and properly configured.
Check if the load is too high.
For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DTS.Msg.GetKafkaMetaInfo.NoAvailableBroker

Error scenarios	Possible cause	Solution
You configure a Kafka destination instance whose version is 1.0 or later.	The database username or password is incorrect.	Enter the correct database username and password. If authentication is disabled for the Kafka instance, leave both fields blank.
	DTS cannot retrieve metadata from the Kafka service.	Verify that the bootstrap.servers parameter is correctly set on the server side. Verify that the Kafka version selected for the destination database is correct. Verify network connectivity.

DTS.Msg.GetMongoDbShardInfo.EmptyInstances

Scenario: You configure a MongoDB task whose source or destination database is a sharded replica set.

Possible cause: DTS cannot retrieve shard information.

Solution: Check your configuration parameters and confirm that the database is a sharded MongoDB instance.

DTS.Msg.GetMongoDbShardInfo.NoShardAddress

Scenario: You configure a MongoDB task whose source or destination database is a sharded replica set.

Possible cause: DTS cannot retrieve shard information.

Solution: Check your configuration parameters and confirm that the database is a sharded MongoDB instance. Also ensure that you have applied for a shard endpoint. For more information, see Apply for a shard endpoint.

DTS.Msg.SuspendDenied.JobStatusModifying

Scenario: You pause a task or batch-pause multiple tasks.

Possible cause: To prevent data inconsistency, DTS prevents you from pausing tasks while they are modifying synchronization objects.

Solution:

For a single task: Wait until the synchronization object modification completes.
For batch pausing: Remove tasks that are modifying synchronization objects, or wait until the modification completes.

DTS.Msg.ModifyDenied.JobStatusNotRunning

Scenario: You modify synchronization objects for a paused task.

Possible cause: To prevent data inconsistency, synchronization objects can be modified only when the task's Status is Running.

Solution: Start the task and wait for it to run normally before you modify synchronization objects.

Note

If the task latency exceeds 10 minutes, do not modify synchronization objects.

DTS.Msg.LXPayOrder.AmountLimitExceeded

Scenario: Payment fails after you configure a task.

Possible cause: Accounts with a POC tag can make only zero-value payments. Payments that exceed zero fail.

Solution:

Use a cash coupon to make the payment amount zero.
Use another account to pay.

Note

You must cancel orders that failed to be paid in the 费用与成本 instead of trying to pay for them again.

DTS.Msg.LXPayOrder.AccountBookNotExists

Scenario: Payment fails after you configure a task.

Possible cause: Your Alibaba Cloud funding account is not activated or your account balance is insufficient.

Solution: Recharge your account to activate your Alibaba Cloud funding account and ensure a sufficient balance, and then repurchase.

Note

You must cancel orders that failed to be paid in the 费用与成本 instead of trying to pay for them again.

DTS.Msg.ConfigJob.NoneSelectedStep

Scenario: You configure a task using the API.

Possible cause: No task type is configured because the StructureInitialization, DataInitialization, and DataSynchronization parameters are all set to false.

Solution: Specify the correct values for these fields to define the task type.

DTS.Msg.ConfigJob.InvalidDbListFormat

Scenario: You configure a task using the API.

Possible cause: The DbList field is not a valid JSON string.

Solution: Pass a correctly formatted string parameter.

DTS.Msg.ConfigJob.InvalidReserveFormat

Scenario: You configure a task using the API.

Possible cause: The Reserve field is not a valid JSON string.

Solution: Pass a correctly formatted string parameter.

DTS.Msg.DistributedDatabaseNodesError

Scenario: You purchase a synchronization instance whose source database is a distributed database, and then configure it.

Possible cause: The value of the source database parameter Number of Distributed Database Nodes does not match the actual number of nodes.

Solution: When you purchase an instance, select the actual Number of Distributed Database Nodes.

DTS.Msg.LXQueryOrder.NotFoundNormalOrder

Error scenarios	Possible cause	Solution
You upgrade or downgrade an instance or change its billing method.	The instance is completed but not released.	Release the completed short-term instance.
	The instance is released but still appears in the console.	For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DTS.Msg.GetSSLInfo.NoSSLConn

This error scenario occurs if you select SSL Secure Connection when configuring a task.

Possible cause: SSL is not enabled for the database instance, so no SSL endpoint exists.

Resolution: You can enable SSL for the database instance or select Non-encrypted Connection.

DTS.Msg.ModifyDynamicConfig.InvalidStatus

Scenario: You modify performance settings for a purchased synchronization or migration instance.

The task may not be in the Running state.

Resolution: The task must be Running before you can proceed.

DTS.Msg.TransferInstanceClass.NoPermission

Scenario: You downgrade an instance.

Possible cause: The account used for downgrading lacks the required permissions.

Solution: Grant the required permissions for the downgrade operation to both the account that performs the operation and its root account. For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DTS.Msg.OperationDenied.ConsumerGroupOutOfUsage

Scenario: You create a consumer group for a subscription instance.

Possible cause: The subscription instance already has 20 consumer groups.

Solution: Delete unused consumer groups based on business requirements and retry.

DTS.Msg.GrantAccessAlreadyExists

Scenario: You configure a DTS task.

Possible cause: A transient error occurred.

Solution: Please retry. If the error persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DTS.Msg.DbListIsEmpty

Error scenarios	Possible cause	Solution
You configure a task using the API.	The DbList field is null or equivalent to null.	Provide a valid DbList value. For more information, see Migration, synchronization, or subscription objects.
You configure a synchronization task.	When you configure a sync task, you do not move databases or tables to Selected Objects, but only move objects such as stored procedures, views, or functions to Selected Objects. Note Synchronization tasks must include at least one database or table.	To configure a migration task with the data migration feature, select Migration Types and enable Schema Migration.

DTS.Msg.GetRedisNodes.NotCluster

Scenario: You configure a Redis task.

Possible cause: The selected Instance Mode is incorrect for the instance.

Resolution: Select the correct Instance Mode for your Redis instance.

DTS.Msg.InvalidDestinationEndPointRegion

Scenario: You configure a task using the API.

Possible cause: The region of the destination instance is invalid or unsupported.

Resolution: To find a valid region, refer to the Region ID column in Supported regions.

DTS.Msg.InvalidSourceEndPointRegion

Scenario: You configure a task using the API.

Possible cause: The region of the source instance is invalid or unsupported.

Solution: For more information, see Supported regions.

DTS.Msg.AdminAccountExists

Scenario: You configure a DTS task.

Possible cause: DTS creates a privileged account in some source databases. If your database already has an account with the same name, the task fails.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DTS.Msg.NotSupportModify

Scenario: You use the ModifyDtsJob API operation to modify a task.

Possible cause: The DtsInstanceId parameter is the migration instance ID.

Solution: Currently, migration tasks support only ETL configuration changes in the console. To modify other settings, you must create a new task.

DTS.Msg.PrePayNotAllowDelete

Scenario: You release a DTS task using the API.

Possible cause: Subscription instances cannot be directly released.

Solution: To release a task, see Release a DTS instance.

DTS.Msg.Forbidden.AliyunUIDNotFound

Scenario: You configure a task in the DTS console, especially for cross-account tasks or when you log on with a RAM user.

Possible cause: The Alibaba Cloud account (root account) that is used to log on to the DTS console is not initialized.

For cross-account tasks, the Alibaba Cloud account (root account) that owns the source database instance has never logged on to the DTS console.
When you use a RAM user, the Alibaba Cloud account (root account) that owns the RAM user has never logged on to the DTS console.

Solution: View the UID in the pop-up error message and log on to the DTS console with the root account to retry.

DTS.Msg.RamPermissionDenied

Scenario: You perform operations in the DTS console using a RAM user.

Possible cause: The RAM user lacks the required permissions.

Solution: Grant permissions to the RAM user and retry. For more information, see Authorize a RAM user to manage DTS or Custom policies for Data Transmission Service.

Note

When you create a custom policy, use the Action (API operation name) and ResourceId (DTS instance ID) provided in the error message.

错误提示

DTS.Msg.EcsJoinSecurityGroupLimitExceeded

Error scenario: You configure a task that uses an ECS-hosted database as the data source.

Possible cause: The ECS instance belongs to more than five security groups.

Solution: Review your business requirements and remove excess security groups from the ECS instance and retry. For more information, see Remove a security group.

Note

If all security groups are required, you can consolidate them into five or fewer.

DTS.Msg.UpgradeTrialTimesLimit

Scenario: You try the RPS upper limit upgrade feature.

Possible cause: You have exceeded the maximum number of trials. Each account can try this feature three times, and each trial lasts 24 hours.

Solution: None.

DTS.Msg.HasRunningTrial

Scenario: You try the RPS upper limit upgrade feature.

Possible cause: The DTS instance is already using this feature and cannot start another trial.

Solution: None.

DTS.Msg.DtsInstanceHasNoLimit

Scenario: You try the RPS upper limit upgrade feature.

Possible cause: The DTS instance has no RPS limits, so the feature is unavailable.

Solution: None.

DTS.Msg.UpgradeTrialInvalidJobStatus

Scenario: You try the RPS upper limit upgrade feature.

Possible cause: This feature is supported only for DTS instances in the Running, Paused, or failed state.

Solution: None.

DTS.Msg.InvalidMigrationJobId

Scenario: You configure a task using the API.

Possible cause: The job ID is invalid or the task has been deleted.

Solution: Retry with a valid parameter.

DTS.Msg.InvalidIpAddress

An error occurs if you configure a DTS task for a database instance and the Connection Type is set to Public IP, Leased Line/VPN Gateway/Smart Access Gateway, or Cloud Enterprise Network (CEN).

Possible cause: The IP address format is invalid and cannot be parsed.

Solution: Enter a valid IP address and retry.

DTS.Msg.PauseDenied.JobStatusNotRunning

Scenario: You pause a task.

Possible cause: The task is in a state other than Running, such as failed, paused, or initializing.

Resolution: Fix the issue or wait until the task status is Running, and then pause the task.

DTS.Msg.CheckpointOutOfAdjustableRange

This error occurs if you modify the position during the Incremental Write phase.

Possible cause: The specified position is outside the modifiable range.

Solution: Modify the position within the allowed range.

DTS.Msg.MaxRetryTime.Invalid

An error occurs if you modify the Retry Time After Source or Destination Database Disconnection setting.

Possible cause: The value is outside the valid range of 10 to 1440 minutes.

Resolution: Set the Retry Time After Source or Destination Database Disconnection parameter to a value within the valid range. We recommend a value of at least 30 minutes.

DTS.Msg.CrossRegionJobTransferToCluster

Scenario: You migrate a DTS shared cluster instance to a dedicated cluster.

Possible cause: The source and destination databases of the shared cluster instance are in different regions. Cross-region tasks are not supported for migration to dedicated clusters.

Solution: None.

DTS.Msg.JobNotInClusterRegion

Scenario: You migrate a DTS shared cluster instance to a dedicated cluster.

Possible cause: The region of the shared cluster instance differs from the region of the dedicated cluster. DTS supports migrating shared cluster tasks only to dedicated clusters in the same region.

Solution: None.

DTS.Msg.CallCloudProductApiError

Scenario: You configure a DTS task.

Possible cause: An error occurs when an OpenAPI operation of another Alibaba Cloud service is called.

Solution: Review the error details, including CloudProduct, ErrCode, and ErrMsg, to identify and resolve the issue.

DTS.Msg.MongoCommandError

Scenario: You configure a MongoDB task.

Possible cause: An error occurs when a MongoDB command is executed.

Solution: Search for a solution in the official MongoDB documentation based on the command and the specific error message.

DTS.Msg.RedisCluster.NotSupportClassicNetworkEcs

Scenario: You configure a Redis task using the API.

Possible cause: DTS does not support Redis cluster instances that are hosted on ECS in classic networks.

Solution: None.

DTS.Msg.NotSupportRedisMinorVersion

Scenario: You configure a Redis task using the API.

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

Solution: Upgrade the Redis instance to a supported minor version and reconfigure the task. For more information, see Upgrade minor version.

DTS.Msg.DtsInstanceNotExists

Scenario: You query DTS instance details using the API.

Possible cause: The DTS instance does not exist.

Solution: None.

DTS.Msg.NotPurchaseDtsInstance

Scenario: You modify full or incremental rates for a DTS task using the API.

Possible cause: The DTS instance for the task is not purchased, so rate adjustments are unavailable.

Solution: Purchase the DTS instance before you make modifications.

DTS.Msg.NotSupportJobType

Scenario: You query performance monitoring data using the API.

Possible cause: The task type does not support performance monitoring queries.

Solution: None.

DTS.Msg.MysqlCommandError

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

Possible cause: An error occurs when the MySQL command is executed.

Solution: Consult the official MySQL documentation for solutions.

DTS.Msg.DynamicConfigError

Scenario: You adjust the task rate.

Possible cause: Network jitter causes the rate adjustment to fail.

Solution: Adjust the task rate again.

DTS.Msg.GetVpcError

Scenario: An error occurs during task configuration.

Possible cause: DTS encounters an error when it retrieves VPC instance information.

Solution: Search the official Virtual Private Cloud documentation for a solution based on the specific error message.

DTS.Msg.ListResourceGroupsError

Scenario: An error occurs when you query task details.

Possible cause: An error occurs when resource groups are queried.

Solution: Retry the query.

DTS.Msg.SearchDtsJobLogError

Scenario: You query task logs.

Possible cause: The query time range is too large.

Solution: Narrow the time range and retry.

DTS.Msg.GetDgInstanceError

Scenario: An error occurs during task configuration.

Possible cause: DTS encounters an error when it retrieves a Database Gateway (DG) instance.

Solution: Consult the official Database Gateway (DG) documentation for solutions.

DTS.Msg.JobProgressNotExists

Scenario: You skip a table during full migration.

Possible cause: An error occurs when the table is skipped.

Solution: Retry the operation.

DTS.Msg.GetCenError

Scenario: An error occurs during task configuration.

Possible cause: DTS encounters an error when it retrieves a CEN instance.

Solution: Consult the official Cloud Enterprise Network (CEN) documentation for solutions.

DTS.Msg.GetDgDatabaseError

Scenario: You configure a task whose source or destination is a Database Gateway (DG)-connected instance.

Possible cause: DTS encounters an unknown error when it queries DG instance information.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DTS.Msg.SQLServerError

Scenario: You configure a task whose source or destination database is SQL Server.

Possible cause: An error occurs when a SQL command is executed.

Solution: Consult the official SQL Server documentation for solutions.

DTS.Msg.InvalidDbList

Scenario: You modify synchronization objects for a synchronization task.

Possible cause: The synchronization object parameter format is invalid.

Solution: Ensure that the synchronization object parameter is correct and retry.

DTS.Msg.GetRdsNetInfoError

Scenario: You configure a task whose source or destination is an ApsaraDB RDS instance.

Possible cause: DTS encounters an unknown error when it queries RDS network information.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DTS.Msg.PolarDB.DBDescribeDBClusterAttribute

Scenario: You configure a task whose source or destination is a PolarDB instance (PolarDB for MySQL, PolarDB for Oracle, PolarDB for PostgreSQL, or PolarDB-X).

Possible cause: DTS encounters an unknown error when it queries PolarDB instance information.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DTS.Msg.DgInstanceNotExists

Scenario: You configure a task whose source or destination is a Database Gateway (DG)-connected instance.

Possible cause: The DG instance does not exist.

Solution: None.

DTS.Msg.MongoDB.DescribeDBInstanceAttribute

Scenario: You configure a task whose source or destination is a MongoDB instance.

Possible cause: DTS encounters an unknown error when it queries MongoDB instance information.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DTS.Msg.ClearConfigureContextError

Scenario: You modify synchronization objects for a synchronization task.

Possible cause: An unknown error occurs during synchronization object modification.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DTS.Msg.ModifyCheckpoint.CurrentCheckpointIsEmpty

Scenario: You modify the task position.

Possible cause: The new position is empty.

Solution: Verify the new position parameter and modify it within the allowed range.

DTS.Msg.DbInstanceNotExists

Scenario: You configure a DTS task.

Possible cause: The database instance does not exist.

Solution: None.

DTS.Msg.NotSupportEsInstance

Scenario: You configure a DTS task.

Possible cause: The Elasticsearch instance is unsupported, which causes an error when its network information is queried.

Solution: Use a supported Elasticsearch instance. For information about supported versions, see Synchronization solutions and Migration solutions.

DTS.Msg.AliyunDbsError

Scenario: You configure a physical protocol migration task for SQL Server.

Possible cause: An error occurs when the DBS API is called.

Solution: Troubleshoot the issue based on the DBS API error information.

DTS.Msg.ScheduleJobError

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

Possible cause: The system is temporarily unavailable.

Solution: Retry after a short period.

DTS.Msg.InvalidPort

Scenario: You configure a DTS task.

Possible cause: The port parameter is invalid.

Solution: Enter a valid port number.

DTS.Msg.ModifyDtsJob.NoIncrementalWriteModule

Scenario: You modify synchronization objects.

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

Solution: Verify that the task is a synchronization task. Only synchronization tasks support modifying synchronization objects.

DTS.Msg.ModifyDtsJob.HasCanNotRestartIncrementalWriteModule

Scenario: You modify synchronization objects.

Possible cause: The task has an incremental write module that cannot restart.

Solution: Ensure that the incremental write module is in the Running, Paused, or Failed state before you modify synchronization objects.

DTS.Msg.ModifyDtsJob.HasNotSyncedIncrementalWriteModule

Scenario: You modify synchronization objects.

Possible cause: The task has an incremental write module that is not running.

Solution: Wait until the incremental write module starts, and then modify the synchronization objects.

Abnormal.RamCheckUserRole

Scenario: You create a task.

Possible cause: Your Alibaba Cloud account (root account) has not authorized the default DTS role (AliyunDTSDefaultRole).

Solution: Authorize the DTS default role and retry. For more information, see Grant DTS access to cloud resources.

Forbidden.InstanceNotFound

Scenario: You configure a DTS task.

Possible cause: The instance does not exist.

Solution: Ensure that the instance ID is correct and retry.

InvalidJobId

Scenario: You configure a DTS task.

Possible cause: The DTS task does not exist.

Solution: Ensure that the DTS task ID is correct and retry.

InternalError

Scenario: You configure a DTS task.

Possible cause: DTS encountered an internal error.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

RdsGetInstanceAttr.InvokeFail

Scenario: You configure a DTS task.

Possible cause: DTS encounters an error when it queries RDS instance information.

Solution: Troubleshoot the issue based on the specific error message.If the issue cannot be resolved, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

LXCreateOrder.InvokeFail

This error occurs when you purchase a DTS instance.

Possible cause: A transient error occurred.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DbProductInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the OpenAPI of another Alibaba Cloud service is called.

Solution: Troubleshoot the issue based on the information returned by the OpenAPI of other Alibaba Cloud products.If you cannot resolve the issue, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

InvalidParameter

Scenario: You configure a task using the API.

Possible cause: The input parameter does not meet the requirements.

Solution: Provide valid parameter values.

DTS.Msg.CreateSubDistriubtedJobError

Scenario: You configure a DTS task.

Possible cause: An error occurs when a distributed task is created.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

NotFound.UserDBInstanceList

Scenario: You configure a DTS task.

Possible cause: An error occurs when database instances are queried.

AssumeRoleFail

Scenario: You configure a cross-Alibaba Cloud account task.

Possible cause: The cross-account role name (RAM role name) is incorrect.

Solution: Verify the cross-account role name. For more information, see Synchronize an RDS MySQL instance across Alibaba Cloud accounts.

OperationDenied.JobStatus

Scenario: You configure a DTS task.

Possible cause: The current task state does not allow the requested operation.

Solution: Ensure that the task state meets the operation requirements, and then retry.

NetWorkItemNotFound

Scenario: You configure a DTS task.

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

Solution: Ensure that the database network type matches the instance's network type.

EcsJoinSecurityGroup.InvokeFail

Scenario: You configure a DTS task.

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

Solution: Troubleshoot the issue based on the specific error message. For more information, see the FAQ in Add a security group rule.

SQLExecuteError

Scenario: You configure a DTS task.

Possible cause: An SQL execution exception occurred.

NoPermission

Scenario: You configure a task using a RAM user.

Possible cause: The RAM user lacks the required permissions.

Solution: Grant permissions to the RAM user and retry. For more information, see Authorize a RAM user to manage DTS or Custom policies for Data Transmission Service.

PolarDbGetNetworkItems.InvokeFail

Scenario: You configure a task whose source or destination is a PolarDB instance (PolarDB for MySQL, PolarDB for Oracle, PolarDB for PostgreSQL, or PolarDB-X).

Possible cause: DTS encounters an unknown error when it queries PolarDB instance information.

InvalidRpsValue

Scenario: You adjust the task rate.

Possible cause: The RPS value does not meet the requirements.

Solution: Use a valid RPS value as indicated in the error message.

RdsInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the RDS OpenAPI is called.

InvalidTaskStatus

Scenario: You modify synchronization objects.

Possible cause: The task has an incremental write module that is not running.

Solution: Wait until the incremental write module starts, and then modify the synchronization objects.

PolarDbGetWhiteNames.InvokeFail

Scenario: You configure a task whose source or destination is a PolarDB instance (PolarDB for MySQL, PolarDB for Oracle, PolarDB for PostgreSQL, or PolarDB-X).

Possible cause: An unknown error occurs when the PolarDB instance allowlist is retrieved.

ADB30GetNetworkItems.InvokeFail

Scenario: You configure a task whose destination is an AnalyticDB for MySQL instance.

Possible cause: An unknown error occurs when network information for the AnalyticDB for MySQL instance is retrieved.

QueryInstanceConnection

Scenario: You configure a DTS task.

Possible cause: Retrieving database instance network information failed.

RdsGetInstanceList.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the RDS instance list is retrieved.

RdsGetWhiteNames.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the RDS instance allowlist is retrieved.

InvalidParameter.TagValue

Scenario: You create a tag.

Possible cause: The tag value does not meet the requirements.

Solution: Set a valid tag value and retry.

RamPermissionCheckFailed

Scenario: You configure a DTS task.

Possible cause: DTS encounters an error when it checks RAM user permissions.

Solution: Please retry. If the error persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

RdsModifyWhiteName.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the RDS instance allowlist is modified.

DmsInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the DMS OpenAPI is called.

InvalidParameter.DStoreDataRange

Scenario: You modify the task position.

Possible cause: The specified position is outside the modifiable range.

Solution: Modify the position within the allowed range.

InvalidStepId

Scenario: You configure a DTS task.

Possible cause: The step ID does not exist in the task configuration.

Solution: Ensure that the step ID is correct and retry.

IllegalJdbcUrl

Scenario: You configure a DTS task.

Possible cause: The JDBC connection URL for the database instance is invalid.

Solution: Configure the task using a valid JDBC connection URL.

InvalidRegion.NotFound

Scenario: You configure a DTS task.

Possible cause: The specified region does not exist.

Solution: Use a valid region when you configure the task.

MissingParameter

Scenario: You configure a DTS task.

Possible cause: A required parameter is missing from the request.

Solution: Ensure that all request parameters are complete and correct, and then retry.

AliyunProductInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when an OpenAPI operation of another Alibaba Cloud service is called.

Solution: Review the error details, including CloudProduct, ErrCode, and ErrMsg, to identify and resolve the issue.

DTS.Msg.OperationDenied.JobStatus

Scenario: You configure a DTS task.

Possible cause: The current task state does not allow the requested operation.

Solution: Retry when the task state meets the requirements.

OperationDenied.DBInstanceStatus

Scenario: You configure a DTS task.

Cause: The running status of the RDS instance configured for the task is not set to Running.

Ensure that the status of the RDS instance is Running before you retry.

InvalidInstanceId

Scenario: You configure a DTS task.

Possible cause: The database instance used for the task does not exist.

Solution: Ensure that the database instance ID is correct and retry.

InvalidStepCode.NotAllowed

Scenario: You pause the incremental data collection module.

Possible cause: The incremental data collection module does not support pausing.

Solution: None.

InvalidJobType.NotToWay

Scenario: You reverse the direction of a bidirectional synchronization task.

Possible cause: The task type does not support reversing the direction.

Solution: None.

InvalidJobType.NotSupport

Scenario: You reverse the direction of a bidirectional synchronization task.

Possible cause: The task type does not support reversing the direction.

Solution: None.

InvalidJobStatus

Scenario: You reverse the direction of a bidirectional synchronization task.

Possible cause: The task state does not support reversing the direction.

Confirm that the Status of the forward and reverse sync jobs is Running or Paused, and then retry.

HbaseueNetWorkItemNotFound

Scenario: You configure a DTS task.

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

Solution: Ensure that the database network type matches the instance's network type.

InvalidSslConfig

Scenario: You configure a DTS task.

Possible cause: Saving the SSL TrustStore failed.

Solution: Please retry. If the error persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

VpcInvokeFail

Scenario: You configure a DTS task.

Possible cause: DTS encounters an error when it connects to the database instance.

Solution: Please retry. If the error persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

QueryInstanceAttr

Scenario: You configure a DTS task.

Possible cause: Retrieving database instance information failed.

QueryInstanceWhiteList

Scenario: You configure a DTS task.

Possible cause: Querying the database instance allowlist failed.

HbaseueModifyInstanceWhiteList

Scenario: You configure a DTS task.

Possible cause: Querying the database instance allowlist failed.

CreateAccountFail

Scenario: You configure a DTS task.

Possible cause: DTS failed to create a database account.

ModifyAccountFail

Scenario: You configure a DTS task.

Possible cause: Database account authorization failed.

DTS.Msg.ModifyDbListFail

Scenario: You modify synchronization objects for a synchronization task.

Possible cause: An error occurs when synchronization objects are modified.

Solution: Please retry. If the error persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DropAccountFail

Scenario: You configure a DTS task.

Possible cause: Deleting the database account failed.

QueryAccountFail

Scenario: You configure a DTS task.

Possible cause: Querying the database account failed.

AccountExists

Scenario: You configure a DTS task.

Possible cause: The database account already exists.

RedisInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the Redis OpenAPI is called.

RedisError

Scenario: You configure a DTS task.

Possible cause: An error occurs when the Redis instance is connected.

DRDSInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when a PolarDB-X 1.0 (formerly DRDS) database instance is connected.

DTS.Msg.InvalidDrdsTable

Scenario: You configure a DTS task.

Possible cause: An error occurs when table topology information for PolarDB-X 1.0 (formerly DRDS) is retrieved.

Solution: Ensure that the table topology information in the error message is correct, and then retry.If the issue cannot be resolved, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DTS.Msg.MissingUserName

Scenario: You configure a DTS task.

Possible cause: An error occurs when the AccessKey ID of the MaxCompute (formerly ODPS) instance owner is verified.

Solution: Ensure that the owner's AccessKey ID is correct and retry.

DTS.Msg.MissingPassword

Scenario: You configure a DTS task.

Possible cause: An error occurs when the AccessKey secret of the MaxCompute (formerly ODPS) instance owner is verified.

Solution: Ensure that the owner's AccessKey secret is correct and retry.

PolarDbInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when database instance information is retrieved.

GpdbInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when database instance information is retrieved.

EcsInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when database instance information is retrieved.

AdsV3InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when database instance information is retrieved.

DTS.Msg.InvalidDbListError

Scenario: You configure a DTS task.

Possible cause: An error occurs when synchronization objects are validated.

Solution: Ensure that synchronization objects are correctly configured and retry.

ADB30GetWhiteNames.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the allowlist for an AnalyticDB for MySQL instance is retrieved.

ADB30ModifyWhiteName.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the allowlist for an AnalyticDB for MySQL instance is modified.

ADB30GetInstanceList.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the AnalyticDB for MySQL instance list is retrieved.

ADB30GetDbClusterAttr.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when cluster information for an AnalyticDB for MySQL instance is retrieved.

DescribeResourceUsage.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when RDS instance resource usage is queried.

DescribeDatabases.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when RDS instance information is queried.

RdsGetInstanceConnection.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when RDS instance database connection information is queried.

RdsCreateUserAccount.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when an RDS instance account is created.

RdsGetNetworkItems.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when RDS instance database connection information is queried.

HbaseueGetNetworkItems.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when HBase instance database connection information is queried.

GetNetworkItems.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when database connection information is retrieved.

RdsGetRegions.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when RDS instance region information is retrieved.

RdsCreateMigrateTask.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when a migration task whose source or destination is an RDS instance is created.

RdsDescribeMigrateTaskById.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when a migration task whose source or destination is an RDS instance is queried.

MongoDbGetWhiteNames.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the MongoDB instance allowlist is retrieved.

MongoDbGetInstanceList.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the MongoDB instance list is retrieved.

MongoDbGetInstanceConnection.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when MongoDB instance database connection information is retrieved.

MongoDbGetShardingMongoConnection.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when MongoDB instance sharding node connection information is retrieved.

MongoDbModifyWhiteNames.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurred while the whitelist of the MongoDB instance was modified.

MongoDbGetInstanceAttr.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when MongoDB instance information is retrieved.

MongoDbGetShardingMongoGidInvokeFail.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the GID of a MongoDB instance sharding node is retrieved.

PolarDbGetInstanceList.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the PolarDB instance list is retrieved.

PolarDbGetInstanceConnection.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when PolarDB instance connection information is retrieved.

PolarDbModifyWhiteNames.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the PolarDB instance cluster allowlist is modified.

PolarDbGetInstanceAttr.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when PolarDB instance information is retrieved.

RedisGetWhiteNames.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the Redis instance allowlist is retrieved.

RedisGetInstanceList.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the Redis instance list is retrieved.

RedisGetInstanceConnection.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the Redis instance endpoint is retrieved.

RedisModifyWhiteNames.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the Redis instance allowlist is modified.

RedisGetInstanceAttr.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when Redis instance information is retrieved.

RedisGetNetworkItems.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the Redis instance endpoint is retrieved.

RedisCreateAccount.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when a Redis instance account is created.

RedisGetComputingType.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the Redis instance architecture type is retrieved.

EcsGetWhiteNames.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the ECS instance allowlist is retrieved.

EcsGetInstanceList.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the ECS instance list is retrieved.

EcsGetMetricList.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the ECS instance metric list is retrieved.

EcsGetInstanceConnection.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when ECS instance network information is retrieved.

EcsModifySecurityGroup.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the ECS instance security group is modified.

EcsAuthSecurityGroup.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the ECS security group is called.

EcsLeaveSecurityGroup.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the ECS instance security group is removed.

EcsGetInstanceAttr.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when ECS instance information is retrieved.

EcsGetSecurityGroupAttr.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when the ECS instance security group is retrieved.

EcsDelSecurityGroup.InvokeFail

Scenario: You configure a DTS task.

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

EcsRevokeSecurityGroup.InvokeFail

Scenario: You configure a DTS task.

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

EcsGetNetworkItems.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when ECS instance security group rules are retrieved.

EcsCreateAccount.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when an ECS account is created.

LindormGetNetworkItems.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when Lindorm instance database connection information is retrieved.

LindormGetVpcAddress.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when Lindorm instance database connection information is retrieved.

LindormGetInstanceAttr.InvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when Lindorm instance information is retrieved.

InvalidOperation.AdvanceAction

Scenario: You modify the task position.

Possible cause: The task does not have an incremental data collection module and does not support position modification.

Solution: None.

TablestoreInvokeFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when database instance information is retrieved.

UnSupported

Scenario: You configure a DTS task.

Possible cause: The current task does not support this operation.

UnSupportedTaskType

Scenario: You configure a DTS task.

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

CheckJobCreateFail

Scenario: You configure a DTS task.

Possible cause: Creating the validation task failed.

Solution: Please retry. If the error persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

ConfigurationDtsJobFail

Scenario: You configure a DTS task.

Possible cause: Creating a task whose source or destination database instance is Db2 for i (AS/400) failed.

AllSiteInnerApiSupportFail

Scenario: You configure a DTS task.

Possible cause: An error occurs when a database account is created.

Missing.TagKey

Scenario: You add a tag to a DTS instance.

Possible cause: The tag key is not set.

Solution: Set a valid tag key and retry.

MissingParameter.TagOrResourceId

Scenario: You add a tag to a DTS instance using the API.

Possible cause: The instance ID, tag key, or tag value is missing from the parameters.

Solution: Ensure that all parameters are complete and correct, and then retry.

InvalidParameter.ResourceType

Scenario: You query or add a tag using the API.

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

Resolution: Set the ResourceType parameter to ALIYUN::DTS::INSTANCE and retry the operation.

InvalidParameter.TagKey

Scenario: You query or add a tag using the API.

Possible cause: The tag key does not meet the requirements.

Solution: Set a valid tag key and retry.

InvalidResourceId.NotFound

Scenario: You query or add a tag using the API.

Possible cause: The DTS instance does not exist.

Solution: Ensure that the DTS instance ID (ResourceId) is correct and retry.

InvalidParameter.Tags

Scenario: You query or add a tag using the API.

Possible cause: The tag key or value does not meet the requirements.

Solution: Set a valid tag key and value, and then retry.

InvalidParameter.NextToken

Scenario: You query or add a tag using the API.

Possible cause: An error occurs when the tag is parsed.

Solution: Please retry. If the error persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

InvalidParameter.Category

Scenario: You query all tags using the API.

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

Resolution: Set the Category parameter to Custom (for user-added tag keys) or System (for system-created tags) and retry.

NumberExceed.Tags

Scenario: You add a tag to a DTS instance.

Possible cause: The number of tags added in a batch exceeds 20.

Note

Each instance can have up to 20 tags.

Solution: Reduce the number of tags and retry.

NumberExceed.ResourceIds

Scenario: You add a tag to a DTS instance.

Possible cause: The number of DTS instances exceeds 50.

Note

You can attach tags to up to 50 instances at a time.

Solution: Reduce the number of instances and retry.

Duplicate.TagKey

Scenario: You add a tag to a DTS instance.

Possible cause: A duplicate tag exists.

Solution:

Method 1: Modify the tag key and retry.
Method 2: If your business allows, remove the duplicate tag and retry.

QuotaExceed.TagsPerResource

Scenario: You add a tag to a DTS instance.

Possible cause: The total number of tags exceeds 20.

Note

Each instance can have up to 20 tags.

Solution: If your business allows, delete unused tags and retry.

NoPermission.SystemTag

Scenario: You add a tag to a DTS instance.

Possible cause: An error occurs when tags are queried.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

NoPermission.Operator

Scenario: You add a tag to a DTS instance.

Possible cause: An error occurs when tags are queried.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

UnsupportedTaskRegion

Scenario: You configure a dedicated cluster task.

Possible cause: Dedicated clusters do not support cross-region tasks.

Solution: None.

UnsupportedDtsJob

Scenario: You configure a dedicated cluster task.

Possible cause: The current task does not support this operation.

Solution: None.

UnsupportedDtsInstance

Scenario: You configure a dedicated cluster task.

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

Solution: None.

UnsupportedTransferType

Scenario: You configure a dedicated cluster task.

Possible cause: DTS does not support migration tasks across dedicated clusters.

Solution: None.

DedicatedClusterReleased

Scenario: You configure a dedicated cluster task.

Possible cause: The dedicated cluster has been released.

Solution: None.

DedicatedClusterReleasing

Scenario: You configure a dedicated cluster task.

Possible cause: The dedicated cluster is being released.

Solution: None.

OperationDenied.DedicatedClusterStatus

Scenario: You configure a dedicated cluster task.

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

Solution: None.

OperationDenied.DedicatedClusterUsedDu

Error scenarios	Possible cause	Solution
You configure a dedicated cluster task.	The dedicated cluster has insufficient available DUs.	Increase the dedicated cluster's overcommit ratio and retry. For more information, see Set the overcommit ratio for a DTS dedicated cluster. Note The maximum overcommit ratio is 200%.
You configure a dedicated cluster task.	The specified dedicated cluster does not exist.	Purchase a new dedicated cluster and retry. For more information, see Create a DTS dedicated cluster.

DedicatedClusterAllocateDuFail

Scenario: You configure a dedicated cluster task.

Possible cause: An error occurs when DUs for the dedicated cluster are allocated.

Solution: Please retry. If the error persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

JobProgressNotFound

Scenario: You skip a table during full migration.

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

Solution: None.

LXBuyError

Scenario: You purchase a DTS instance.

Possible cause: An error occurs when the instance is purchased.

Solution: Please retry. If the error persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

SourceIpIsNotAllowedToConnect

Scenario: You configure a DTS task.

Possible cause: An error occurs when the source public IP address is verified.

Solution: Please retry. If the error persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DestIpIsNotAllowedToConnect

Scenario: You configure a DTS task.

Possible cause: An error occurs when the destination public IP address is verified.

Solution: Please retry. If the error persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

MissingDtsInstanceId

Scenario: You configure a DTS task.

Possible cause: The DTS instance ID is missing from the request parameters.

Solution: Verify that the request parameters are correct.

RgPreCheckFailed

Scenario: You configure a DTS task.

Possible cause: An error occurs when the resource group is checked.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

RgOperationFailed

Scenario: You configure a DTS task.

Possible cause: An error occurs when the resource group is checked.

Solution: Please retry. If the error persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

RgRegionNotSupport

Scenario: You configure a DTS task.

Possible cause: An error occurs when the resource group is checked.

Solution: Please retry. If the error persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

MissingDestinationEndpointPort

Scenario: You configure a DTS task.

Possible cause: The destination instance port is missing from the request.

Solution: Ensure that all request parameters are complete and correct, and then retry.

MissingSourceEndpointPort

Scenario: You configure a DTS task.

Possible cause: The source instance port is missing from the request.

Solution: Ensure that all request parameters are complete and correct, and then retry.

DTS.Msg.NotSupportSubscribeJob

Scenario: You modify a subscription task in the new console.

Possible cause: The task is an old version, and the new console does not support modifying old subscription tasks.

Resolution: Go to the Change Tracking tab in the DMS console. In the lower-right corner, click jiqiren and then 返回旧版 to return to the old DTS console and modify the task.

DTS.Msg.VpcSubnetIpExhaust

Scenario: You create a consumer group for a subscription task.

Possible cause: The virtual switch configured for the task has an insufficient number of available IP addresses.

Solution: Ensure that the virtual switch configured for the task has a sufficient number of available IP addresses, and then retry.If the issue persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DTS.Msg.GetCenVpcError

Scenario: You configure a task whose source or destination instance uses a CEN connection.

Possible cause: An error occurs when the VPC list under the CEN is retrieved.

Ensure that the CEN instance ID is correct and retry.If the issue persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

DTS.Msg.InvalidMongoDBStatus

Scenario: You configure a task whose source or destination is a MongoDB instance.

Possible cause: The MongoDB instance is in an invalid state.

Solution: Check the MongoDB instance status and retry after it returns to normal.

SQLException: Misconfigured master - master server_id is 0

This error scenario occurs when you configure a job.

Possible cause: The source database server_id check failed.

Solution: Change the server_id to an integer greater than 1 that is unique among all databases, and then retry. For more information, see Source database server_id check.

Common errors during task runtime

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

Possible cause: You did not select schema migration or synchronization during task configuration, and you did not create the corresponding table in the destination database. As a result, the table does not exist in the destination database.

Solution:

Method 1: For a synchronization task, use the Modify Synchronization Objects feature to remove the problematic table from the synchronization objects. For more information, see Remove synchronization objects.
Method 2: Manually create a table with the same schema as the source table in the destination database, and then restart the task.

For example, the following error message indicates that the dts_order table does not exist in the destination database. To resolve this error, create the dts_order table in the destination database according to the source table, and then restart the task.

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 are missing from the source or destination database.

Solution: Choose a solution based on the task type and module.

Data synchronization task:
- If the incremental write module reports an error, check if the corresponding table exists in the destination database and if its schema is consistent. If the table does not exist:
  1. Use the Modify Synchronization Objects feature to remove the problematic table from the synchronization objects.
  2. Clear the data from the problematic table in the destination database.
  3. Use the Modify Synchronization Objects feature to add the table back to the synchronization objects.
  4. Resume the task.
- If the full migration module reports an error, check if the corresponding table exists in both the source and destination databases and if their schemas are consistent. If the table does not exist, reconfigure the task.
Data migration task: Ensure that the schemas of the tables to be migrated are consistent between the source and destination databases, and then reconfigure the task.

Error example:

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 destination database account information was modified during task runtime, which causes a connection failure. For example, the password was changed, permissions were modified, or the account was deleted.

Solution:

Method 1: Restore the account information in the destination database. If the task has already failed, restart it after you restore the account.
Method 2: Reconfigure the task with an account that has the correct permissions and password.

The following is an example of an error message indicating that the root account cannot connect to the destination database.

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 retrieves the table schema, no worker nodes are available in AnalyticDB for MySQL.

Solution: Check if the AnalyticDB for MySQL database is available.

Error example:

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 missing from the destination table.

Solution:

Method 1 (Recommended): Add the missing column to the destination table, and then start the task.
Method 2:
Important Do not use this method for bidirectional synchronization tasks, if the destination table receives data from sources other than DTS, or if the destination table is part of a many-to-one synchronization architecture. This includes scenarios where multiple tables in one task or tables from multiple tasks map to a single destination table.
1. Remove the problematic table from the synchronization objects, and then start the task. For more information, see Remove synchronization objects.
2. Take one of the following actions:
  - If the synchronization task includes schema synchronization, delete the table in the destination database.
  - If the synchronization task does not include schema synchronization, delete the table in the destination database and recreate it with the same schema as the source.
3. Add the table back to the synchronization objects. For more information, see Add synchronization objects.

For example, the following error message indicates that the wx_state column is missing from the dts_user_authorization table in the destination database.

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

Recommendation: A missing column can have several causes. One common cause is adding a column to the source database when the synchronization link does not support DDL synchronization. To avoid this, add the column to the destination database first, and then to the source database.

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

Possible cause 1: The data write module timed out while it connected to the cache module due to network jitter or other issues.

Solution 1: Restart the task and check if it resumes normally.

Possible cause 2: The task has been delayed for too long.

Resolution 2: The task cannot be recovered. In the Actions column for the task instance, choose > Reconfigure Task.

Error example:

Failed to get offsets by times in 60000 ms

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

Possible cause: The log cannot be found. The source log may have been cleared.

Solution: Reconfigure the task.

Error example:

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: The DDL operation is not supported by the link, which causes the DDL execution to fail.

Solution:

For partial database synchronization: Resynchronize the table. Remove it from the synchronization objects, delete the table in the destination database, and then add it back. DTS performs a full synchronization, including schema retrieval, which bypasses this DDL operation.
For full database synchronization: In AnalyticDB for MySQL, create a new table with a different name but the same schema as the source table. Use INSERT INTO SELECT to copy data from the source table to the new table. Delete the problematic table, and then use RENAME to rename the new table to the original name. Restart the task.

Error example:

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 was paused for too long, and the data at the corresponding position is no longer in the DTS cache module.

Solution 1: First, try to modify the instance's position. If the issue persists, choose one of the following solutions. For more information about how to modify the position, see Modify the current position of a synchronization or migration instance.

Check if the time range of the incremental data parsing log, such as a binary log or redo log, in the source database includes the specified timestamp. If it does, try to reread the data from the backend. If not, create a new task.
Create a new task.
Important
Do not pause tasks for extended periods. The maximum pause duration for a successful restart is 7 days. This period may be shorter if the source database has a high data write volume.

Possible cause 2: The task failed for too long, and the data at the corresponding position is no longer in the DTS cache module.

Solution 2: Create a new task.

Important

If a task fails, resolve the issue and resume the task promptly to avoid recovery failure due to prolonged downtime.

Possible cause 3: Full migration or synchronization took too long, and DTS may have cleared the cached data logs from the task's start time. This results in incomplete logs for incremental parsing.

Note

During full migration or synchronization, DTS locally stores the source database's data logs for the last 24 hours or up to 50 GB for incremental data parsing.

Solution 3: Create a new task. Before you create the task, estimate the data volume. If it is large, consider splitting it into multiple migration or synchronization tasks.

Error example: The following error message indicates that the data at the position (2021-5-20 21:17:51) is no longer in the DTS cache module.

Note

The value 1660802171 in the error message is a Unix timestamp in seconds. You can convert this timestamp to UTC with a Unix timestamp converter.

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: The DDL operation is not supported by the link, which causes the DDL execution to fail.

Solution:

For partial database synchronization: Resynchronize the table. Remove it from the synchronization objects, delete the table in the destination database, and then add it back. DTS performs a full synchronization, including schema retrieval, which bypasses this DDL operation.
For full database synchronization: In AnalyticDB for MySQL, create a new table with a different name but the same schema as the source table. Use INSERT INTO SELECT to copy data from the source table to the new table. Delete the problematic table, and then use RENAME to rename the new table to the original name. Restart the task.

Error example:

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 destination database account lacks the required permissions.

Solution: Grant the required command permissions to the DTS user account in the destination database.

Error example:

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 specified in the error message does not exist in the destination database.

Solution: Check if the table exists in the destination database. If not:

Method 1: For a synchronization task, use the Modify Synchronization Objects feature to remove the problematic table from the synchronization objects. For more information, see Remove synchronization objects.
Method 2: Manually create a table with the same schema as the source table in the destination database, and then restart the task.

Error example:

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 if the destination Elasticsearch service is running normally.

Error example:

{"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: A database connection exception occurred.

Solution: Check if the database connection is normal, and then restart the task. For more information, see Source database connectivity check and Destination database connectivity check.

Error example:

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 connection was reset.

Solution: Check the network status and test the connection to the database.

Error example:

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: An index in a source table is corrupted, which prevents data from being read.

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

The following is an example of an error message indicating that an index for the mytable table is corrupted.

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

You can use the following commands to repair it:

use my_database;
repair table mytable;

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

Possible cause: A column is missing from the destination table.

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

Error example:

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

Possible cause:

Cause 1: The disk is full.
Cause 2: The table size has reached its limit.

Solution:

Method 1: Expand the disk space, and then restart the task.
Method 2: Resolve the table size limit at the database level, and then restart the task.
Note
For MySQL databases, see the official documentation for table size limits.

Error example:

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 full

Possible cause:

Cause 1: The disk is full.
Cause 2: The table size has reached its limit.

Solution:

Method 1: Expand the disk space, and then restart the task.
Method 2: Resolve the table size limit at the database level, and then restart the task.
Note
For MySQL databases, see the official documentation for table size limits.

Error example:

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: A database connection exception occurred.

Solution: Check if the database connection is normal, and then restart the task. For more information, see Source database connectivity check and Destination database connectivity check.

Error example:

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, and the database address or port is incorrect.

Solution 1: Correct the database address and port information, and then restart the task.

Possible cause 2: The database is connected to DTS via a leased line, and the connection is abnormal.

Solution 2: Check the leased line's route table and firewall configuration.

Error example:

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 may have been released.

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

Error example:

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

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

Possible cause: The database connection limit has been reached.

Solution: Increase the database connection limit, and then restart the task.

Error example:

Too many connections@error code:1040

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

Possible cause: The DTS connection request was refused.

Solution: Check your allowlist and authorization settings.

Error example:

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 SQL Server database connection was interrupted.

Solution: Ensure that the source and destination SQL Server databases are connectable, and then restart the task.

Error example:

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

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

Possible cause: The connection was reset due to network instability.

Solution: Ensure that the SQL Server database is connectable, and then restart the task.

Error example:

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: An Elasticsearch service connection exception occurred.

Solution: Check if the Elasticsearch service connection is normal, and then restart the task.

Error example:

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 used in the DTS task has expired.

Solution: Follow the original MySQL error message to change the password and reset the expiration time. We recommend that you set it to never expire.

Synchronization task: Reconfigure the password for the DTS task.
Migration task: Recreate the link.

Error example:

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 used for the task lacks the required permissions.

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

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

Solution 2: DTS does not support synchronizing or migrating data from the admin and local databases.

Error example:

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: A database connection exception occurred.

Solution: Check if the database connection is normal, and then restart the task. For more information, see Source database connectivity check and Destination database connectivity check.

Error example:

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 timed out while the latest binary log position from the source database was retrieved.

Solution: Ensure that DTS can connect to the source database, and then restart the task.

Error example:

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 database connection timed out.

Solution: Ensure that DTS can connect to the database, and then restart the task.

Error example:

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 database is not connectable.

Solution: Ensure that DTS can connect to the database, and then restart the task.

Error example:

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: An exception occurred in the incremental data collection module.

Solution: Restart the incremental data collection module.

Error example:

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 destination database is not connectable.

Solution: Ensure that DTS can connect to the destination database, and then restart the task.

Error example:

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 was paused for more than 7 days, or the MySQL binary log retention period is too short, which causes the binary log to be unavailable.

Solution:

For a self-managed MySQL database: Try to restore the MySQL binary log. If it cannot be restored, create a new task.
For an ApsaraDB RDS for MySQL database: Create a new task.

Error example:

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 exception occurred when the transaction's GTID was retrieved.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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 Oracle archived log space or the root directory is full, which prevents the archiving task from running.

Solution: Check if the Oracle archived log space or the root directory is full.

Error example:

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 used for the task lacks the required permissions.

Solution 1:

Method 1: Grant sufficient permissions to the database account, and then restart the task.
Method 2: Reconfigure the task with a database account that has sufficient permissions.

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

Solution 2:

Synchronization task: Use the Modify Synchronization Objects feature to remove the problematic database from the synchronization objects, and then restart the task. For more information, see Remove synchronization objects.
Migration task: Reconfigure the task and do not select the problematic database.

Error example:

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 database configuration. For more information, see Strange MySQL "read-only" error.

Error example:

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: Field type mapping failed because you did not use DTS for schema migration or synchronization.

Solution: Correct the destination table schema to support type mapping for the problematic field. For more information, see Tried to parse field as object, but found a concrete value.

Error example:

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: The destination database name was changed during task runtime, which causes a connection failure.

Solution: Check if the database exists and ensure that it is connectable.

Error example:

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 destination database name was changed, which causes the schema to be unavailable.

Solution: Check if the schema exists.

Error example:

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: The MySQL instance is in an abnormal state, such as LOCK_WRITE, which prevents DTS from writing data.

Solution: Check if the MySQL instance is in a normal state.

Error example:

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 is missing a primary key.

Solution: Add a primary key to the destination table that matches the primary key of the corresponding source table, and then restart the task.

For example, the following error message indicates that the my_table table in the reader database is missing a primary key. Add a primary key to the my_table table in the destination database based on the source table, and 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 jitter or other issues.

Solution: Restart the incremental write module and check if the task resumes normally.

Error example:

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 jitter or other issues.

Solution: Restart the incremental data collection module and check if the task resumes normally.

Error example:

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 missing from the destination table.

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

Example: The following error message indicates that the a column is missing from the default$default table in the destination database.

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 a high load or network instability.

Solution:

Method 1: On the details page of the migration instance, you can go to Task Management > Full Migration > Adjust Rate to reduce the full migration rate and lower the write load on the destination database.
Method 2: Upgrade the destination database specifications to improve write performance.

Error example:

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: DTS full migration cannot migrate a global index.

Solution 1: Delete the global_index from the destination database.

Possible cause 2: The database storage engine is MyISAM, which DTS does not support.

Solution 2:

Synchronization task: Use the Modify Synchronization Objects feature to remove the problematic table from the synchronization objects, and then restart the task. For more information, see Remove synchronization objects.
Migration task: Reconfigure the task and do not select the problematic table.

Error example:

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 1: Create the corresponding table in the destination database. To delete the table, do so after the task is complete.

Possible cause 2: The database storage engine is MyISAM, which DTS does not support.

Solution 2:

Synchronization task: Use the Modify Synchronization Objects feature to remove the problematic table from the synchronization objects, and then restart the task. For more information, see Remove synchronization objects.
Migration task: Reconfigure the task and do not select the problematic table.

For example, the following error message indicates that the dw.tmp_smb2021 table does not exist in the destination 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: Failed to query the corresponding table schema from the source database. The table may have been deleted, or the source database account lacks query permissions.

Solution 1: Confirm that the table exists in the source database. If it has been deleted, reconfigure the DTS task. If it exists, ensure that the source database account has query permissions for the table.

Possible cause 2: The database storage engine is MyISAM, which DTS does not support.

Solution 2:

Synchronization task: Use the Modify Synchronization Objects feature to remove the problematic table from the synchronization objects, and then restart the task. For more information, see Remove synchronization objects.
Migration task: Reconfigure the task and do not select the problematic table.

Error example: The following error message indicates that the schema for the yyy table in the xxx database could not be retrieved.

**
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 corresponding table in the destination database. To delete the table, do so after the task is complete.

For example, the following error message indicates that the hd_new_cctv.tbl_program table does not exist in the destination database.

    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 occurred during data write to the destination database. This is often caused by a trigger in the destination database that is activated by the DTS write operation.

Solution: Check the table information in the error's SQL statement to see if a trigger exists in the destination database. If your business allows, delete the trigger and restart the task.

Error example:

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 the source and destination tables are inconsistent, and a column is missing from the specified destination table.

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

Example error: The following error message indicates that the exception column does not exist in the t_m_class_record_detail table of the destination database.

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 occurred in the destination database.

Solution: If the destination database is MySQL, use the following commands to check the lock status:

SHOW FULL PROCESSLIST;
SELECT * FROM innodb_trx;

Note

After you resolve the issue, restart the task.

Error example:

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: The destination database schema does not exist.

Solution: Manually create the corresponding schema and the tables to be migrated within it in the destination database, and then restart the task.

Error example:

schema in dblist not found in database

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

Possible cause: The destination database schema does not exist.

Solution: Manually create the corresponding schema and the tables to be migrated within it in the destination database, and then restart the task.

Error 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 destination database account lacks write permissions.

Solution: Grant write permissions to the destination database account.

Error example:

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 destination database disk is locked, possibly because it is full.

Solution: Expand the MongoDB disk space in the destination database, and then restart the task.

Error example:

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 table schemas are inconsistent. This occurs when the source column is NULLABLE and the destination column is NOT NULL.

Resolution: Find the problematic table in the destination database. Change the column type to NULLABLE and restart the task.

Error example:

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 source or destination database has too many connections.

Solution: Adjust the maximum connection limit for the source or destination database, and then restart the task.

Note

If the preceding reasons do not apply to your situation, try the following methods:

Check if the source or destination database is running normally.
Check if the account password has been changed.
Ensure that the DTS IP addresses are fully added to the allowlist. For more information, see IP addresses to add to the allowlist when you migrate, synchronize, or subscribe to a local database.
Check if the source or destination database has too many connections.

Error example:

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 filter condition for the synchronization object is incorrectly formatted. The WHERE keyword is not allowed.

Resolution: Remove the WHERE keyword from the Filter Condition field of the synchronization object, then restart the task.

Error example:

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 retrieve data from the incremental data collection module.

Resolution: Troubleshoot the Incremental Data Collection module.

Error example:

\"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 retrieve data from the incremental data collection module.

Solution: Restart the incremental write module and check if the task resumes normally.

Error example:

\"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: The DTS network cannot connect to the Redis instance, or the Redis instance has been released.

Solution: Check if the Redis instance is connectable.

Error example:

\"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: The destination database already contains a key with the same name but a different type as the source key.

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

Error example:

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: The source database does not have a log for the specified timestamp.

Solution: Reconfigure the task.

Error example:

"\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 using Secure Sockets Layer

Possible cause: The database instance is not connectable.

Solution: Ensure that the database can be connected to properly, and then restart the task.If the issue persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

"cause:\n" +
     "\tSQLServerException: The driver could not establish a secure connection to SQL Server 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 log mode is incorrect. DTS requires the binlog_row_image='FULL' mode for MySQL connections.

Solution: Change the binary log mode, clear the data from the destination table during a non-business period, and reconfigure the task. For more information about how to change the binary log mode, see DTS-1051007.

Note

Ensure that the binlog_row_image parameter is set to FULL on the source database before you create the DTS task.

Error example:

\"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 retrieve data from the incremental data collection module.

Solution: Troubleshoot the issue based on the error message from the Incremental Data Collection module, and then restart the task.If the issue cannot be resolved, use DingTalk (DingTalk client download address) to join the DTS customer communication DingTalk group (Group ID: 116655009709) for assistance.

Error example:

\"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 syntax in the error message.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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: The source and destination table schemas are inconsistent, and DTS cannot perform the type conversion.

Solution: Modify the destination table schema to match the source table schema, and then restart the task.

Error example:

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: A database exception occurred.

Solution: Recover the database and restart the DTS instance.

Error example:

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 occurred when DTS was constructing the SQL statement.

Solution: Ensure that the source and destination table schemas are consistent or compatible, and then restart the task. For a synchronization task, you can remove the problematic table from the synchronization objects and restart the task. For more information, see Remove synchronization objects.

Error example:

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 incorrect, which causes the ETL execution to fail.

Solution: Check if the ETL syntax is correct based on the error message.

Error example:

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 configured for the task lacks the required permissions.

Solution: Grant the missing permissions to the DTS task account based on the error message.

Error example:

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: The destination table does not allow modifying columns via DDL operations.

Solution:

Method 1: Temporarily allow the destination table to execute the DDL operation specified in the error message.
Method 2: If your business allows, after the relevant DDL operation is completed on the source table, release the task, clear the data from the destination table, and create a new task.
Note
For synchronization tasks, you can also use the Modify Synchronization Objects feature to resolve this issue after the DDL operation is completed on the source table. For more information, see How do I resolve table-related errors for a synchronization instance?.

Error example:

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 SQL query execution timed out.

Resolution: Run the set max_statement_time=0 command to remove the SQL query time limit, then restart the task.

Error example:

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 destination object does not exist.

Solution 1: Check if the destination object specified in the error message exists.

Possible cause 2: The account used for the task lacks the required permissions.

Solution 2: Check if the account used for the task has sufficient permissions.

Error example:

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 source and destination table columns are incompatible.

Solution:

Method 1: Check if the column mapping feature can resolve the issue. For more information, see Database and table column mapping.
Method 2: If your business allows, modify the destination table schema to match the source table schema, and then reconfigure the task. Restarting the task is not effective.

Error example:

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, you cannot insert data into an auto-increment field in a SQL Server table.

Solution: Set the IDENTITY_INSERT property of the table specified in the error message to ON, and then restart the task.

Error example:

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: A change in the source database prevents data from being queried.

Solution: Wait for DTS to retry automatically.

Error example:

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 occurred in a database transaction.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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 specified in the error message does not exist.

Solution: Check if the table exists in the source and destination databases. If it does not exist in the destination database, manually create it and restart the task.

Error example:

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 a unique constraint.

Solution: Add a primary key or unique constraint to the table, and then restart the task.

Error example:

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 if the topic specified in the error message exists. If not, create it and restart the task. For more information about how to create a topic, see Topic operations.

Error example:

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: A column with a NOT NULL constraint in the destination database is being written with a null value.

Solution: Remove the NOT NULL constraint from the problematic column in the destination database, and then restart the task.

Error example:

 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 RENAME operation failed because the target table name already exists.

Solution: Check if the table with the same name can be deleted. If so, delete it and restart the task.

Error example:

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

The destination may have insufficient disk space.

Solution: Expand the destination database's disk space, and then restart the task.

Error example:

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: A DTS instance allows only one table to have the IDENTITY_INSERT property set to ON, and another table already has it enabled.

Resolution: Set the instance's sink.batch.enable parameter to false and restart the task. For more information, see Modify instance parameters.

Error example:

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 is missing from the destination table.

Solution: Add the missing column to the destination table based on the source table schema and the error message, and then restart the task.

Error example:

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 database's transaction log storage or disk space is full.

Solution: Expand the transaction log storage or disk space, and then restart the task.

Error example:

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 on the target is full.

Solution: Expand the destination database's disk space, and then restart the task.

Error example:

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 the log based on the LSN when the task starts.

Resolution: Set the backup frequency to Same as Data Backup.

Error example:

Position not found:

\"dts-k-src: DTS-52102: retry final failed\n" +
                "cause:\n" +
                "\tRecoverableAnyAllException: dts-k-src: DTS-52110: SQLServerRecordExtractor Init Error: sqlserver-reader: DTS-52061: Failed to seek sqlserver position\n" +
                "\tCriticalAnyAllException: sqlserver-reader: DTS-52061: Failed to seek sqlserver position\n" +
                "\tCriticalAnyAllException: sqlserver-reader: DTS-52411: Fetch backup log failed\n" +
                "\tCriticalAnyAllException: sqlserver-reader: DTS-52061: seek binlog for timestamp 1666324457\"

Invalid SCN:

Fetch *** SQL Server backup log faild, fetch ls  ***

DTS-RETRY-ERR-0107: Fetch (.)? SQL Server backup log faild (.)? fetch ls

Possible cause: SQL Server cannot find the log based on the LSN during task runtime.

Resolution: Set the backup frequency to Same as Data Backup.

Error example:

Position not found

\"dts-k-src: DTS-52102: retry final failed\n" +
                "cause:\n" +
                "\tRecoverableAnyAllException: dts-k-src: DTS-52110: SQLServerRecordExtractor Init Error: sqlserver-reader: DTS-52061: Failed to seek sqlserver position\n" +
                "\tCriticalAnyAllException: sqlserver-reader: DTS-52061: Failed to seek sqlserver position\n" +
                "\tCriticalAnyAllException: sqlserver-reader: DTS-52411: Fetch backup log failed\n" +
                "\tCriticalAnyAllException: sqlserver-reader: DTS-52061: seek binlog for timestamp 1666324457\"

Invalid SCN

Fetch *** SQL Server backup log faild, fetch ls  ***

DTS-RETRY-ERR-0108: Column (.*)? For input string

Possible cause: The data format of the field in the error message is incorrect.

Solution: Correct the data format of the problematic field in the destination database, and then restart the task.

Error example:

**** (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 is missing from the destination table.

Solution: Add the missing column to the destination table based on the source table schema and the error message, and then restart the task.

Error example:

\"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 source connection was disconnected.

Resolution: Check the health of the source database and increase the value of client-output-buffer-limit slave.

Note

Run the config set client-output-buffer-limit 'slave 0 0 0' command to disable the replication output buffer limit.

Error example:

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 was generated during task runtime.

Solution: Check if the source and destination table schemas are consistent.

Error example:

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 was generated during task runtime.

Solution: Check if the source and destination table schemas are consistent.

Error example:

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 specified in the error message does not exist in the destination database.

Solution: Check if the table exists in the destination database. If not:

Method 1: For a synchronization task, use the Modify Synchronization Objects feature to remove the problematic table from the synchronization objects. For more information, see Remove synchronization objects.
Method 2: Manually create a table with the same schema as the source table in the destination database, and then restart the task.

Error example:

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 is missing from the destination table.

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

Error example:

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: Failed to retrieve metadata.

Solution: Check if the database account used for the task has the required permissions and if the table exists in the source database.

Error example:

\"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 current SQL Server instance does not support enabling Change Data Capture (CDC).

Solution: Check if the instance version supports enabling CDC.

Error example:

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: The MongoDB instance is in an abnormal state.

Solution: Check if the MongoDB instance is running normally.

Error example:

\"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 for an index with the same name. If a deletable index with the same name exists, delete it and restart the task.

Error example:

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 MongoDB instance's disk is locked, which prevents data from being written.

Solution: Check if the MongoDB instance's disk is full. If so, expand the instance's storage and restart the task.

Error example:

\"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 specified in the error message, and then restart the task.

Error example:

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 destination instance's disk space is full.

Solution 1: Expand the destination instance's storage and restart the task. If it is a self-managed MySQL database, follow these steps. If it is an ApsaraDB RDS for MySQL database, upgrade its configuration. For more information, see Change configuration.

Log on to the self-managed MySQL database.
In the my.ini configuration file, find the data storage path, which is the value of the datadir parameter.
Go to the data storage path and clear disk space.
Warning
Proceed with caution to avoid accidental data loss.
Restart the MySQL database, and then restart the DTS task.

Error example 1:

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 temporary table has reached its usage limit.

Resolution 2: Increase the temporary table limit. For a self-managed MySQL database, follow these steps. For an ApsaraDB RDS for MySQL database, increase the values of the tmp_table_size and max_heap_table_size runtime parameters within their valid ranges. For more information, see Modify instance parameters.

Log on to the self-managed MySQL database.
You can check the values of the tmp_table_size and max_heap_table_size parameters in the my.ini configuration file.
Note
The default value for tmp_table_size and max_heap_table_size is 16 MB.
- If the parameters are not present, add the following code to the [mysqld] section of the my.ini file:
```
tmp_table_size = 256M
max_heap_table_size = 256M
```
- If the parameter values are too small, increase them.
Restart the MySQL database, and then restart the DTS task.

Error example 2:

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 data being written exceeds the configured value.

Solution: Set the max_allowed_packet parameter to a value that meets your requirements.

Error example: The following error message indicates that the amount of data being written (7956719) exceeds the configured value (6291456).

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 DTS disk space is full.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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 specified in the error message does not exist in the destination database.

Solution: Create the table in the destination database based on the error message and the source table information, and then restart the task.

Error example:

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: A column is missing from the destination table, which causes DTS to fail when it retrieves column information.

Solution 1: Ensure that the corresponding column exists in the table specified in the error message, and then restart the task.

Possible cause 2: The database account used for the DTS task lacks the required permissions, which causes DTS to fail when it retrieves column information.

Solution 2: Ensure that the database account has read and write permissions for the table, and then restart the task.

Possible cause 3: The max_stack_depth parameter of the destination instance is too small.

Solution 3: Increase the value of the max_stack_depth parameter for the destination instance, and then restart the task. For more information about how to modify parameters for an ApsaraDB RDS for PostgreSQL database, see Set instance parameters.

Possible Cause 4: The target Elasticsearch index is a rolling index.

Solution 4: DTS does not currently support scroll indexes.

Possible cause 5: The destination table contains a column with a precision that is incompatible with the source table.

Solution 5: Check the column precision in the source and destination tables. Modify the precision in the destination table as needed, and then restart the task.

Error example:

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 value of max_allowed_packet is smaller than the actual packet size.

Solution: Ensure that the value of max_allowed_packet is set to be larger than the actual packet size, and then restart the task.

Error example:

"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 query for the source database schema timed out.

Solution: Restart the task.

Error example:

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: Failed to pull the oplog based on the timestamp.

Resolution: Ensure that oplog.rs exists in the local database. Then, increase the oplog pull time and reconfigure the task.

Note

DTS does not support incremental tasks with a standalone MongoDB instance as the source.

Error example:

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

To resolve the issue, set the binlog_format parameter to 'row', use the KILL command to close all sessions on the source database, and then reconfigure the task.

Error example:

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 log no longer exists in the source database, so DTS incremental data collection cannot retrieve the corresponding data.

Solution: Reconfigure the task.

Error example:

\"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 1: Check if the corresponding table or view exists.

Possible cause 2: The database account used for the task lacks the required permissions.

Solution 2: Check if the account has read permissions for the corresponding table or view.

Error example:

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 statement executed on the source database is not supported by the destination database's group shard.

Solution:

Synchronization task:
- Method 1: Use the Modify Synchronization Objects feature to remove the corresponding table from the synchronization objects. For more information, see Remove synchronization objects.
- Method 2: Determine if the SQL statement can be skipped. If not, reconfigure the task.
Migration task: Determine if the SQL statement can be skipped. If not, reconfigure the task.

Error example:

\"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 a table index field supported by the MySQL InnoDB engine is 767 bytes.

Resolution: For ApsaraDB RDS for MySQL 5.6 or 5.7, set the innodb_large_prefix parameter of the destination instance to ON, and then restart the task. For more information about modifying parameters, see Modify instance parameters.

Error example:

Specified key was too long; max key length is 767 bytes.

DTS-RETRY-ERR-0143: empty binlog list in oss

Possible cause: DTS cannot retrieve the specified binary log from OSS.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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 retrieve the specified binary log.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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 field specified in the filter condition does not exist in the source database.

Solution:

To modify the objects in a synchronization task, go to the Selected Objects section, right-click the synchronization object, modify the Filter Condition in the dialog box, and complete the configuration.
Migration task: Reconfigure the task with the correct filter condition.

Error example:

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	Solution
The connection between the task and the source database was reset.	Ensure that DTS can connect to the source database, and then start the DTS task.
The DTS IP address range is not fully added to the source database's allowlist.	Ensure that all DTS server IP addresses are added to the security settings of the source database. Then, start the DTS task.

Error example:

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 field specified in the filter condition does not exist in the source database.

Solution:

To modify the objects in a synchronization task, go to the Selected Objects section, right-click the synchronization object, modify the Filter Condition in the dialog box, and complete the configuration.
Migration task: Reconfigure the task with the correct filter condition.

Error example:

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

A possible cause is that the current MySQL database instance does not support the show binary logs command.

Solution: Upgrade the MySQL database instance version, and then restart the task.

Error example:

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 partition corresponding to the destination field does not exist.

Solution: Add the corresponding partition to the destination database, and then restart the task.

Error example:

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: The source database connection failed, which causes DTS initialization to fail.

Solution: Ensure that DTS can connect to the source database, and then restart the task.

Error example:

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 cannot connect to the database due to network issues.

Solution: Ensure that DTS can connect to the database, and then restart the task.

Error example:

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 Oracle log file does not exist.

Solution: Reconfigure the task.

Error example:

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 specified in the error message does not exist in the destination database.

Solution: Create the table in the destination database based on the error message and the source table information, and then restart the task.

Error example:

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 instance is out of memory.

Solution: Upgrade the memory of the destination Redis instance, and then restart the task. For more information about how to expand a Tair (Redis OSS-compatible) instance, see Change instance configuration.

Error example:

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 current database configuration is incorrect.

Resolution: To resolve this issue, manually execute the set log_bin_trust_function_creators = 1 command and then restart the task.

Error example:

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 synchronization or migration object contains a column name with special characters, such as spaces.

Solution: Modify the column name, and then restart the task.

Error example:

jobId=or81144k303****, code=02, errMsg=[13000, 202211302315061921681441470345301****] Incorrect column name: ` ä¸€çº§ç.

DTS-RETRY-ERR-0158: Failed to get global table lock for

Possible cause: The current database does not support transactions that operate on multiple tables.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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: A null value is being written to a column with a NOT NULL constraint in the destination database.

Solution: Modify the destination field's constraint by removing the NOT NULL constraint.

Error example:

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: The log information for the specified position cannot be retrieved.

Solution: Check the log status. If it is abnormal, fix it and restart the task. If it is normal, reconfigure the task.

Error example:

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: can not find index by table

Possible cause: Elasticsearch is missing an index.

Solution: Manually create the index in Elasticsearch, and then restart the task.

Error example:

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 has expired.

Solution: Restart the task.

Error example:

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 database connection limit has been reached.

Resolution: Check the database's maximum connection limit and the number of active connections. If necessary, adjust the max_connections parameter and restart the task.

Error example:

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 exists

Possible cause: The binary log of the source MySQL database instance has been cleared.

Solution:

Method 1: Restore the binary log of the source MySQL database instance, and then restart the task.
Method 2: Reconfigure the task.

Error example:

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: The destination schema does not exist.

Solution: Ensure that the destination schema exists and the task is configured correctly, and then restart the task.

Error example:

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: The unique index does not include all columns in the table's partition function.

Solution: Modify the unique index to include all columns from the table's partition function.

Error example:

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 the primary key column, and the SQL Server UPDATE statement can parse only the before-image values of the clustered index columns.

Solution: Modify the clustered index to include the primary key column, and then restart the task.

Error example:

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: A primary key conflict occurred due to an enabled trigger, which causes the write operation to fail.

Solution: Disable or delete the trigger, and then restart the task.

Error example:

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: An exception occurred in the incremental data collection module.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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: Data write failed due to an enabled foreign key in the destination database.

Solution: Disable or delete the foreign key, and then restart the task.

Error example:

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: The source and destination table schemas are inconsistent, and DTS cannot perform the type conversion.

Solution: Modify the destination table schema to match the source table schema, and then restart the task.

Error example:

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 ETL data processing statement is incorrect. It should use the source table and column names.

Solution: Correct the data processing statement, and then restart the task. For more information about how to modify ETL configurations, see Configure ETL in a DTS migration or synchronization task.

Error example:

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: Cannot connect to the source database.

Solution: Check if the source database information and settings are correct. For more information, see Source database connectivity check.

Error example:

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 database connection limit has been reached.

Resolution: Check the database's maximum connection limit and the number of active connections. If necessary, adjust the max_connections parameter and restart the task.

Error example:

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 source and destination table schemas do not match.

Solution: Modify the destination table schema to match the source column types, and then restart the task.

Error example:

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 keys passed to the Lua script are not in the same slot.

Solution: To ensure atomicity, all keys in a Lua script must be in the same slot. Modify the script accordingly, and then restart the task.

Error example:

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: A SQL syntax error occurred. A comma is not a valid value type.

Solution: Correct the SQL statement, and then restart the task.

Error example:

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 destination schema matching failed.

Solution: Modify the destination table schema to match the source table schema, and then restart the task.

Important

DDL operations are not supported for tasks with the multi-table merge feature enabled.

Error example:

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: A SQL syntax error occurred. The hexadecimal digit is invalid.

Solution: Correct the SQL statement, and then restart the task.

Error example:

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 used for the task lacks the required permissions.

Solution 1:

Method 1: Grant sufficient permissions to the database account, and then restart the task.
Method 2: Reconfigure the task with a database account that has sufficient permissions.

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

Solution 2:

Synchronization task: Use the Modify Synchronization Objects feature to remove the problematic database from the synchronization objects, and then restart the task. For more information, see Remove synchronization objects.
Migration task: Reconfigure the task and do not select the problematic database.

Error example:

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 for the table in the binary log does not match the number of columns in DTS.

Resolution: Check the error message for local count is 0.

If it does: Ensure that the account used for the task has SELECT permissions for the table, and then restart the task.
No.
- Synchronization task: Use the Modify Synchronization Objects feature to remove the problematic table from the synchronization objects, and then restart the task. For more information, see Remove synchronization objects.
- Migration task: Reconfigure the task and do not select the problematic table.

Error example:

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: A database connection exception occurred.

Solution: Check the MySQL database instance version. For information about supported versions, see Synchronization solutions, Migration solutions, and Subscription solutions.

Error example:

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 destination table schema is incompatible with the source data.

Solution: Modify the destination table's column types to match the source, and then restart the task.

Error example:

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 used for the task lacks the required permissions.

Method 1: Grant sufficient permissions to the database account, and then restart the task.
Method 2: Reconfigure the task with a database account that has sufficient permissions.

Error example:

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 database is not connectable.

Solution: Troubleshoot the issue based on the error message.If you cannot resolve the issue, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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 a NOT NULL constraint in the destination database is being written with a null value, either because it was filtered out of the task or because it has no value in the source.

Solution: Modify your business logic to ensure that the data being synchronized or migrated meets the destination database's constraints, and then restart the task.

Error example:

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 tables are inconsistent.

Solution: Modify your business logic to ensure that the unique indexes are consistent, and then restart the task.

Error example:

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 is missing from the destination table.

Solution: Add the missing column to the destination table based on the source table schema and the error message, and then restart the task.

Error example:

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 database connection limit has been reached.

Resolution: Check the database's maximum connection limit and the number of active connections. If necessary, adjust the max_connections parameter and restart the task.

Error example:

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: Failed to retrieve source database information.

Solution: Ensure that the source database is running normally and is connectable, and then restart the task.

Error example:

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 source or destination schema does not exist.

Solution: Ensure that the schema specified in the error message exists in both the source and destination databases, and then restart the task.

Error example:

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 Redis username or password is incorrect.

Solution: Reconfigure the task with the correct Redis username and password.

Error example:

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 exceeded the limit.

Solution: Delete unused topics, and then restart the task. For more information about how to delete a topic, see Topic operations.

Error example:

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 1: Add the corresponding table or view based on the error message, and then restart the task.

Possible cause 2: The database account used for the task lacks the required permissions.

Solution 2: Grant sufficient permissions to the database account, and then restart the task.

Error example:

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 1: Add the corresponding table or view based on the error message, and then restart the task.

Possible cause 2: The database account used for the task lacks the required permissions.

Solution 2: Grant sufficient permissions to the database account, and then restart the task.

Error example:

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 being migrated has dependencies, which causes the VIEW creation to fail.

Solution: Remove the dependencies of VIEW and FUNCTION respectively, and restart the schema migration module.If you cannot resolve the error, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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: A source database connection exception occurred, which prevents DTS from retrieving column information.

Solution: Restart the task.If the error cannot be resolved, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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 being written exceeds the maximum length defined for the column in the table schema.

Solution: Increase the maximum length of the problematic column in the table to accommodate the data, and then restart the task.

Error example:

jobId=ckwu1nn2100****, code=07, errMsg=common: DTS-100047: retry 4151 times, 43201510 seconds, which exceed the supposed 43200 seconds cause:    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 is missing from the destination table.

Solution: Add the missing column to the destination table based on the source table schema and the error message, and then restart the task.

Error example:

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 are missing from the source or destination database.

Solution: Choose a solution based on the task type and module.

Data synchronization task:
- If the incremental write module reports an error, check if the corresponding table exists in the destination database and if its schema is consistent. If the table does not exist:
  1. Use the Modify Synchronization Objects feature to remove the problematic table from the synchronization objects.
  2. Clear the data from the problematic table in the destination database.
  3. Use the Modify Synchronization Objects feature to add the table back to the synchronization objects.
  4. Resume the task.
- If the full migration module reports an error, check if the corresponding table exists in both the source and destination databases and if their schemas are consistent. If the table does not exist, reconfigure the task.
Data migration task: Ensure that the schemas of the tables to be migrated are consistent between the source and destination databases, and then reconfigure the task.

Error example:

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 on the target is full.

Solution: Expand the destination database's disk space, and then restart the task.

Error example:

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 relation does not exist in the destination database.

Solution: Create the relation in the destination database based on the error message, and then restart the task.

Error example:

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 data type being written to the destination database does not match the data type defined in the table schema.

Solution: Modify the destination table schema to match the source table schema, and then restart the task.

Error example:

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 data type being written to the destination database does not match the data type defined in the table schema.

Solution: Modify the destination table schema to match the source table schema, and then restart the task.

Error example:

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 timed out.

Solution: Ensure that the source database is running normally and is connectable, and then restart the task.

Error example:

**** 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: A database connection exception occurred.

Solution: Restart the task.If the error cannot be resolved, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

**** wait millis 300000, active 2, maxActive 100, creating 1, createElapseMillis 26952, createErrorCount 66 ****

DTS-RETRY-ERR-0216: OutOfMemoryError

Possible cause: The task encountered a large object during runtime, which causes an out-of-memory error.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

java.lang.OutOfMemoryError: Requested array size exceeds VM limit ****

DTS-RETRY-ERR-0222: execute statement failed

Possible cause: An error occurred when data was written to the destination database. This is common when the destination is AnalyticDB for MySQL and an invalid time or date is written.

Solution: You can use the Modify Sync Objects feature of the sync task to remove the table that reports an error from the sync object, and then re-add the table. For more information, see How do I resolve table-related errors for a sync instance?.If the issue persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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: A transient error occurred.

Solution: Restart the task.If the error cannot be resolved, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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 source database account used for the task lacks the required permissions.

Solution: Grant sysadmin permissions to the account, and then restart the task. For more information about how to grant permissions, see CREATE USER.

Error example:

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: The DTS network cannot connect to the Redis instance.

Solution: Ensure that the source and destination instance networks are normal, and then restart the task.

Error example:

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 collation rules of the source and destination tables are inconsistent.

Resolution: Ensure the character sets and collation rules of the source and destination tables are consistent, and then restart the task. For example, for MySQL 8.0 and later, you can run the ALTER TABLE XXX default character SET utf8mb4 collate=utf8mb4_general_ci; command to change the default collation rule from utf8mb4_0900_ai_ci to utf8mb4_general_ci.

Note

Replace XXX with the corresponding table name.

Error example:

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 instance is in read-only mode.

Solution: Check if the destination instance can be changed to a regular read-write instance:

If yes: Change the destination instance to a regular read-write instance, and then restart the task.
If no: Reconfigure the task with a regular read-write instance.

Error example:

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 destination Kafka topic does not exist.

Solution: Create the topic in Kafka, and then restart the task. For more information about how to create a topic in Alibaba Cloud Message Queue for Apache Kafka, see Step 1: Create a topic.

Error example:

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 destination account used for the task lacks the required permissions.

Solution: Reconfigure the task with a superuser account.

Error example:

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: Ensure that the Redis instance can connect properly, and then restart the task. If the issue persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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: DTS encountered an error when it retrieved logs.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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: DTS timed out while it read from the source database.

Solution: If your service permits, remove the database timeout limit.If the issue cannot be resolved, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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 retrieve a response from the server.

Solution: Ensure that your network connectivity is normal, and then restart the task. If the issue persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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 instance does not have the character set specified in the error message.

Solution: We recommend that you keep the source and destination database versions consistent or synchronize or migrate from a lower to a higher version to ensure compatibility.

Error example:

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 binary log index information was not updated, and the binary log has been cleared.

Solution: Try to restore the binary log or reconfigure the DTS task.

Error example:

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 data type being written to the destination database does not match the data type defined in the table schema.

Solution: Modify the destination table schema to match the source table schema, and then restart the task.

Error example:

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 MongoDB's authentication database.

Solution: Check if the database username and password used for the task can connect to the database normally.

Error example:

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 data validation task timed out during startup.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

jobId=q6rh1hi510o****, code=05, errMsg=run check job timeout

DTS-RETRY-ERR-0247: cannot execute DELETE in a read-only transaction

Possible cause: A DELETE operation was executed on a read-only node.

Solution: Restart the task.If the error cannot be resolved, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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: DTS timed out while it read from the source database.

Solution: Ensure that DTS can connect to the source database, and then restart the task.

Error example:

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: An object that the SQL statement depends on, such as a function or a trigger's dependent function, does not exist in the destination database.

Solution: Ensure that the dependent object exists in the destination database.

Example: The following error message indicates that the update_version function does not exist in the destination database.

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 execution failed in the destination database.

Solution:

Synchronization task: Use the Modify Synchronization Objects feature to remove the problematic table from the synchronization objects, and then restart the task. For more information, see Remove synchronization objects.
Migration task: Reconfigure the task and do not select the problematic table.

Error example:

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 data type being written to the destination database does not match the data type defined in the table schema.

Solution: Modify the destination table schema to match the source table schema, and then restart the task.

Error example:

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: A network connection failure occurred.

Solution: Ensure that the source database is in a normal state and can be connected, and then restart the task.If the issue cannot be resolved, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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 database (.*)?

Possible cause: Cannot connect to the source database.

Solution: Ensure that the source database is connectable, and then restart the task.

Error example:

jobId=ce7v1agz31w****, errMsg=Failed to connect to database [S124.221.XX.XX:XXX]

DTS-RETRY-ERR-0255: NOSCRIPT No matching script

Possible cause: The source Lua script maps to a cross-slot scenario in the destination database.

Solution: Ensure that the Lua script from the source database is mapped to the same slot in the destination database, and then restart the task.If the issue persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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: Invalid data, such as an invalid date or time, in the data being written to the destination database caused the write operation to fail.

Solution: Modify the destination table schema to match the source table schema, and then restart the task.

Error example:

**** 
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 in the error message is empty and cannot be written to the destination database.

Solution:

Synchronization task: Remove the problematic table or hot table from the synchronization objects, clear the data from the removed table in the destination database, and then add the table back to the synchronization task. For more information, see How do I resolve table-related errors for a synchronization instance?.
Migration task: Please retry.If the error cannot be resolved, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

****  `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 in the destination Elasticsearch database is incorrect, which causes the data write to fail.

Solution: Modify the format of the date field in the destination Elasticsearch database based on the source data and the error message, and then restart the task.

Error example:

****
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 database connection limit has been reached. This exceeds the max_user_connections limit.

Solution: Increase the database's maximum connection limit, and then restart the task. For more information about how to adjust parameters for ApsaraDB RDS for MySQL, see "has more than 'max_user_connections'" or "has exceeded the 'max_user_connections'" error when connecting to an ApsaraDB RDS for MySQL instance.

Error example:

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 instance is not connectable.

Error example:

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 instance in the current task.

Solution: Enable the database backup feature for the self-managed SQL Server instance, and then restart the task. For more information, see Preparations.

Error example:

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 support synchronizing or migrating SCRIPT scripts from Redis instances.

Solution: Ensure that the source Redis instance does not have any SCRIPT scripts, and then restart the task.If the issue cannot be resolved, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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 currently support Redis 7.0 or later.

Solution: None.

Error example:

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: PolarDB-X databases in DRDS mode do not support partitioning.

Solution:

Method 1: Correct the DDL by removing the partition information, and then restart the task.
Method 2: Reconfigure the task with a PolarDB-X database in AUTO mode.

Error example:

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 to be created already exists in the destination database.

Solution: If your business allows, delete the index specified in the error message from the destination database, and then restart the task.

Error example:

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 source table's encoding format.

Solution:

Method 1: If your business allows, modify the source database's encoding format, and then restart the task.
Method 2: Correct the DDL in the destination database, and then restart the task.

Error example:

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 specified in the error message does not exist in the destination database, which causes dependent objects to fail to be created.

Solution: Check the validity of the object. If it is invalid, ignore the object and then restart the task.If the issue cannot be resolved, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

jobId=ofyn25r1t4b****, errMsg=Invalid column name 'TotalAmount'. Invalid column name 'wx_flag'.

DTS-RETRY-ERR-0268: Invalid object name (.*)?

Possible cause: An object that the current task depends on is invalid.

Solution: Confirm if the dependent object exists in the source database.

If it exists: Add the dependent object as a synchronization or migration object.
If it does not exist: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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 encoding of the problematic object is inconsistent with the destination database's encoding.

Solution: Ensure that the source and destination encodings are consistent based on the error message, and then restart the task.

Error example:

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: Creating the MongoDB index timed out.

Solution: Restart the task. If the issue persists, increase the DDL execution timeout for MongoDB, and then restart the task.

Error example:

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 validation task found inconsistent data.

Solution: This error indicates that the full validation task has successfully identified data inconsistencies between the source and destination databases.

If your Full Validation Mode is set to HASH validation by sampling ratio, you can view or download the validation report from the Validation Details tab in the Actions column to find details about any data inconsistencies.
If your Full Validation Mode is set to Validate by table row count, the number after the error message indicates the total number of inconsistent rows. You can view the names of the inconsistent tables on the Validation Details tab.

Error example:

**** 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 ETL configuration from the current task.

Error example:

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, which causes a deadlock when the current task attempts to write data.

Solution: If your business allows, pause data writes from other users to the destination.If the issue cannot be resolved, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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: Failed to read data from the source database.

Solution: Ensure that the problematic table in the source database can be read normally, and then restart the task.

Error example:

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 being written to a column with a NOT NULL constraint in the destination database.

Solution: If your business allows, modify the destination table schema by removing the NOT NULL constraint, and then restart the task.

Error example:

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 Elasticsearch is empty.

Solution: Reconfigure the task and set a filter condition to exclude data with empty string values when you select synchronization or migration objects. For more information, see Set filter conditions.

Error example:

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 current primary key of the schema does not match the information retrieved by DTS.

Solution: Recreate the task.If the issue cannot be resolved, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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 occurred when DTS connected to the database instance.

Solution: Check network allowlists and other settings to ensure that the database is connectable, and then restart the task. For more information, see Source database connectivity check and Destination database connectivity check.

Error example:

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 batch writes and requires the batch feature to be disabled.

Solution: For assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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: Ensure that DTS can connect to the source and destination Redis instances, and then restart the task.

Error example:

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 the current version of the Redis instance, which causes RDB parsing to fail.

Solution: Configure the task using a Redis instance that is supported by DTS.If the error persists, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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 occurred when DTS connected to the database instance.

Error example:

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 Oracle database account has expired, which prevents DTS from connecting to the database.

Solution: Fix the database account, for example, by changing the password in the database, and ensure that DTS can connect to the Oracle database with the updated credentials.

Error example:

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 failed 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'); command on the source database to check whether long-running transactions are blocking slot creation. If long-running transactions exist, wait for them to end and then retry. If the issue persists, use DingTalk (Download DingTalk) to join the DTS Customer Support DingTalk Group (Group number: 116655009709) for assistance.

Error example:

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 account used for the task lacks the required permissions, which causes RDB parsing to fail.

Solution: Refer to the relevant configuration documents to verify that the permissions of your Redis account meet the requirements. If the permissions do not meet the requirements, grant the correct permissions to the account and retry. If the permissions meet the requirements, for assistance, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) on DingTalk (download the client).

Error example:

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: The source database is not readable or writable.

Solution: Ensure that the source database is readable and writable, and then restart the task.

Error example:

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

DTS-RETRY-ERR-0287: Value (.*)? for monthOfYear must be in the range

Possible cause: The date value in the source database is not in a standard format.

Solution:

Synchronization task:
- Method 1: You can use the ETL feature to convert the invalid value. For more information, see Configure ETL in a DTS migration or synchronization task.
- Method 2: Correct the value in the source database, and then use the Modify Synchronization Objects feature to remove and re-add the problematic table. For more information, see Modify synchronization objects.
Migration task: You can use the ETL feature to convert invalid values. For more information, see Configure ETL in a DTS migration or synchronization task.

Error example:

DTS-077100: Record Replicator error in table hdd_ams.ams_****. cause by [java.sql.SQLException: [15018, 202407231646521720170412240345328****] Cannot parse "0000-00-23 15:30:00": Value 0 for monthOfYear must be in the range [1,12]] About more information in [https://****].

DTS-RETRY-ERR-0288: Invalidate value(.*)? , `year` must be between 1 and 9999

Possible cause: The date value in the source database is not in a standard format.

Solution:

Synchronization task:
- Method 1: You can use the ETL feature to convert the invalid value. For more information, see Configure ETL in a DTS migration or synchronization task.
- Method 2: Correct the value in the source database, and then use the Modify Synchronization Objects feature to remove and re-add the problematic table. For more information, see Modify synchronization objects.
Migration task: You can use the ETL feature to convert invalid values. For more information, see Configure ETL in a DTS migration or synchronization task.

Error example:

DTS-100047: retry 178 times, 1805948 seconds, which exceed the supposed 1800 seconds cause: RuntimeException: Table '`welife****`.`welifehy_welife****`' with columns [`couponId`, `bid`, `cType`, `cSids`, `cAids`, `cName`, `cAmount`, `cValidityType`, `cStartTime`, `cEndTime`, `cValidityDate`, `cValidityDateUnit`, `cSummary`, `cCreator`, `cModifier`, `cCreated`, `cUpdated`, `cDeleted`, `cStatus`, `cLimited`, `wcid`, `cEnabled`, `cProductIds`, `cGiftCouponAmountCustom`, `cLimitTotalAmount`, `cLimitCuponNumber`, `cMixUse`, `cUsingTime`, `cFlag`, `cChannel`, `cCardImg`, `mid`, `cUsingScope`, `cSubCoupons`, `cBelongToPack`, `UpdateTime`, `cGiveFriend`, `cFileder`, `cFiledTime`, `cLimitType`, `cProductExtIds`, `cLimitCoupon`, `cValidTimes`, `cShowName`, `cGiveChannel`, `cSaleMoney`, `cSaleMoneyPriorityRule`, `cAddCardBag`, `cOtherName`, `cDateType`, `cLimitMaxAmount`, `cLimitProductType`, `cExtend`, `cImages`, `cSyncBusifavor`, `cAttribute`, `cPlatform`, `cThirdId`] and batch exception is {[13000, 202407201755101921681291090315124****] (Column => WELIFEHY_WELIFE_COUPONS.CFILEDTIME), Invalidate value=>0000-01-01 00:00:00.0, `year` must be between 1 and 9999} BatchUpdateException: [13000, 2024072017551019216812910903151249727] (Column => WELIFEHY_WELIFE_COUPONS.CFILEDTIME), Invalidate value=>0000-01-01 00:00:00.0, `year` must be between 1 and 9999 MySQLSyntaxErrorException: [13000, 2024072017551019216812910903151249727] (Column => WELIFEHY_WELIFE_COUPONS.CFILEDTIME), Invalidate value=>0000-01-01 00:00:00.0, `year` must be between 1 and 9999

DTS-RETRY-ERR-0289: Source data value(.)? doesn't match target field(.)? with type(.*)?

Possible cause: The source and destination databases have columns with inconsistent types, which causes the DTS write operation to fail.

Note

This may be caused by a failed DDL synchronization. You can check the task logs for failed DDL statements. For more information about how to view task logs, see Query task logs.

Solution:

Synchronization task:
- Method 1: Modify the destination table schema to match the source table schema, and then restart the task.
- Method 2: If the task includes schema synchronization, use the Modify Synchronization Objects feature to remove and re-add the problematic table. For more information, see Modify synchronization objects.
Migration task: Modify the destination table schema to match the source table schema, and then restart the task.

Error example:

DTS-100047: retry 4282 times, 43200702 seconds, which exceed the supposed 43200 seconds cause: JdbcUtilsException: jdbc-utils: DTS-11001: jdbc-utils: DTS-11001: Source data value:[course] doesn't match target field:`module` with type:INTEGER, Please check the data types of the source table fields. This issue may be caused by the failure of executing DDL to convert field types on the target side. The failed DDL execution records can be found in dts job's action.log. targetDatabase:new_soke_preview targetTable:approval_templatetargetField: module INTEGER not nullable as module utf8 JdbcUtilsException: jdbc-utils: DTS-11001: Source data value:[course] doesn't match target field:`module` with type:INTEGER, Please check the data types of the source table fields. This issue may be caused by the failure of executing DDL to convert field types on the target side. The failed DDL execution records can be found in dts job's action.log. NumberFormatException: For input string: "course"

DTS-RETRY-ERR-0290: Record Replicator error in table (.)?. cause by (.)? Access denied for (.*)?

Possible cause: The account used for the task lacks the required permissions to execute the corresponding SQL statement.

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

Error example:

DTS-077100: Record Replicator error in table mengniu****.osp_sales_plan****. cause by [java.sql.SQLException: [10000, 2024071715225419216806623903151151449] Access denied for INSERT, check db/table/column is MENGNIU_YIPANHUO/OSP_SALES_PLAN_DETAIL/SALES_AREA_CODE, user:mengniu_**** host:% has privilege: UserPrivilege{globalPrivileges=[EXECUTE, INDEX, PROCESS, SELECT, SHOW VIEW, RELOAD, REFERENCES], dbPrivileges={}, tablePrivileges={}, columnsPrivileges={}}] About more information in [https://****].

DTS-RETRY-ERR-0291: column (.*)? is not nullable, can not set null

Possible cause: A null value is being written to a column with a NOT NULL constraint in the destination table.

Solution: If your business allows, modify the destination table schema by removing the NOT NULL constraint, and then restart the task.

Error example:

DTS-100047: retry 179 times, 1800006 seconds, which exceed the supposed 1800 seconds cause: RuntimeException: Table '`basic_supp****`.`dict_diagn****`' with columns [`id`, `org_id`, `icd_code`, `diagnosis_name`, `morphological_code`, `pinyin`, `wbm`, `search_code`, `search_instructions`, `diagnostic_instructions`, `diagnostic_type`, `scope_outpatient`, `scope_inpatient`, `scope_emergency`, `infection`, `special_disease`, `enable_state`, `disease_report`, `remark`, `create_by`, `gmt_create`, `modify_by`, `gmt_modify`, `active`, `scope_emergency_keep`, `code`, `global_code`, `scope_physical_examination`, `gmc_id`, `out_validate_classify`] and batch exception is {[13000, 202407171426491720160012290315104****] syntax error :column 'DICT_DIAGN****.GMT_CR****' is not nullable, can not set null} BatchUpdateException: [13000, 202407171426491720160012290315104****] syntax error :column 'DICT_DIAGN****.GMT_CR****' is not nullable, can not set null MySQLSyntaxErrorException: [13000, 202407171426491720160012290315104****] syntax error :column 'DICT_DIAGN****.GMT_CR****' is not nullable, can not set null

DTS-RETRY-ERR-0292: can not find disperser for field (.)? with value type (.)?

Possible cause: The data types of the source and destination columns are mismatched and cannot be converted.

Resolution:

Synchronization task:
- Method 1: Modify the destination table schema to match the source table schema, and then restart the task.
- Method 2: If the task includes schema synchronization, use the Modify Synchronization Objects feature to remove and re-add the problematic table. For more information, see Modify synchronization objects.
Migration task: Modify the destination table schema to match the source table schema, and then restart the task.

Error example:

DTS-100047: retry 4320 times, 43204014 seconds, which exceed the supposed 43200 seconds cause: RuntimeException: Table '`adb_jarvi****`.`jarvis_s****`' with columns [`id`, `org_id`, `factory_id`, `putout_category_id`, `bundle_id`, `handle_amount`, `is_putout_all`, `handle_time`, `remark`, `create_time`, `update_time`, `timestamp`] and batch exception is {can not find disperser for field handle_amount DOUBLE nullable as handle_amount utf8 with value type IntegerNumeric} SQLException: can not find disperser for field handle_amount DOUBLE nullable as handle_amount utf8 with value type IntegerNumeric

DTS-RETRY-ERR-0293: db not found. use `show databases` to see all dbs.

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

Resolution: Manually create the database or schema in the destination database, grant sufficient permissions to the account used for the task, and then restart the task.

Error example:

db not found. use `show databases` to see all dbs. current schemas ****

DTS-RETRY-ERR-0294: Invalid default value for (.*)?

Possible cause: The default value for a field's type mapping is invalid. This error can occur during schema synchronization or migration.

Solution: Create the table manually at the destination. Then, skip the table in the Schema Migration module.

Error example:

Invalid default value for 'active_****'. ****

DTS-RETRY-ERR-0295: Do not have enough privileges to use this database

Cause: The database account used by the task has insufficient permissions.

Solution:

Method 1: Grant sufficient permissions to the database account, and then restart the task.
Method 2: Reconfigure the task with a database account that has sufficient permissions.

Error example:

amacadbu**** do not have enough privileges to use this database.. ****

DTS-RETRY-ERR-0296: This connection has been closed

Possible cause: The connection was closed because the source or destination database is in an abnormal state.

Solution: Ensure that the source and destination databases are in a Normal state and can be connected. Then, restart the task.

Error example:

DTS-61015: Create connection failed (url: 10.25.XX.XX:XX/testdbuser01, user: testdbuser01) cause: PSQLException: This connection has been closed.

DTS-RETRY-ERR-0297: cannot execute (.*)? in a read-only transaction

Possible cause: The source database is a read-only database or is in read-only mode.

Solution:

If the source database is a read-only database, you can use a writable source database and reconfigure the task.
If the source database is in read-only mode, you can set the database to read-write mode and restart the task.

Error example:

ERROR: cannot execute CREATE FUNCTION in a read-only transaction

DTS-RETRY-ERR-0298: only (.*)? table allowed

Possible cause: A limit is set on the number of tables in the destination database.

Solution: Contact the database administrator (DBA) for the destination database to remove this limit. Then, restart the task.

Error example:

[17020, 202408021111130210411290680315193****] only 2500 table allowed.

DTS-RETRY-ERR-0300: unknown work mode (.*)?

Possible cause: The configured write mode is not supported for the full data migration task.

Solution: Change the sink.worker.type parameter for the full data migration task to a supported write mode, and then restart the task. For more information, see Modify instance parameters.

Example error:

DTS-31004: unknown work mode bach

DTS-RETRY-ERR-0301: Invalid character data was found

The character sets of the source and destination tables are incompatible. As a result, data cannot be written to the destination database.

You can modify the character set of the destination table and restart the task.

Error example:

truncated CriticalAnyAllException: postgresql: DTS-11002: Invalid character data was found.

DTS-RETRY-ERR-0302: (.*)? is none in where causes

Possible cause: The Filter Conditions for the DTS instance is incorrect.

Solution:

For a synchronization instance: Modify the statement in the Filter Conditions and restart the task. For more information, see What to do next.
For a migration instance: Restart the task. If the task cannot be recovered, reconfigure the task.

If the issue persists, use DingTalk (Download DingTalk client) to join the DTS Customer Communication group (Group ID: 116655009709) for assistance.

Error example:

TransactionReplicateException: transaction-replicate: DTS-71001: MysqlRelatedTextSqlBuilderTools: record **** msg is none in where causes.

DTS-RETRY-ERR-0303: The size of attribute column (.*)? has exceeded the max length

Possible cause: The data in a column exceeds the maximum length defined for the column in the destination database.

Solution: Increase the maximum length of the affected column in the destination database table to accommodate the data. Then, restart the task.

Error example:

DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 43200 seconds cause: ClientException: The size of attribute column 'task_i****' has exceeded the max length: 2097152.

DTS-RETRY-ERR-0306: Error while parsing column ETL value for command

Possible cause: The ETL process failed because the data processing statement for Extract, Transform, and Load (ETL) is incorrect.

Solution:

For a synchronization instance: Review the error message and correct the data processing statement. Then, restart the task. For more information, see Configure ETL for a DTS migration or synchronization task.
For a migration instance: Reconfigure the migration task and enter the correct data processing statement.

Error example:

ETL: DTS--0001: Error while parsing column ETL value for command e_switch ****

DTS-RETRY-ERR-0307: Writer has been closed

Possible cause: Data cannot be written to the destination database.

Solution: Ensure that the incremental change logs for the source database are available, the destination database is in a Normal state with a structure compatible with the source database, and the destination database account has the required permissions. Then, restart the task.

Error example:

DTS-100047: retry 15 times, 15 seconds, which exceed the supposed 922337203685477**** seconds cause: IOException: Writer has been closed.

DTS-RETRY-ERR-0308: Error while executing ETL

Possible cause: The extract, transform, and load (ETL) task failed due to an error in the data processing statements.

Solution:

For a synchronization instance: Review the error message and correct the data processing statement. Then, restart the task. For more information, see Configure ETL for a DTS migration or synchronization task.
For a migration instance: Reconfigure the migration task and enter the correct data processing statement.

Error example:

DTS-31009: In process of processing data (recordRange: 330151334436352****) failed cause: FatalAnyAllException: common: DTS-100047: retry 4251 times, 43201 seconds, which exceed the supposed 43200 seconds CriticalAnyAllException: ETL: DTS--0001: Error while executing ETL: e_switch ****

DTS-RETRY-ERR-0310: Function (.*)? not found

Possible cause 1: The function specified in the error message does not exist in the destination database.

Solution 1: Create the function in the destination database. The function name is provided in the error message, and the function definition is in the source database.

Possible cause 2: The destination database does not support functions.

Solution 2: Reconfigure the DTS task.

Example error:

DTS-31009: In process of processing data (recordRange: 782344968821171****) failed cause: FatalAnyAllException: common: DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 43200 seconds DbException: Function "UNIX_TIMESTAMP" not found [90022-193] JdbcSQLException: Function "UNIX_TIMESTAMP" not found [90022-193]

DTS-RETRY-ERR-0311: MongoExecutionTimeoutException: operation exceeded time limit

Cause: The destination MongoDB database timed out during a change operation.

Solution: If your business operations permit, remove the database timeout limit or upgrade the database specifications, and then restart the task.

Error example:

FatalAnyAllException: common: DTS-100047: retry 1 times, 45662 seconds, which exceed the supposed 43200 seconds RuntimeException: com.mongodb.MongoExecutionTimeoutException: operation exceeded time limit MongoExecutionTimeoutException: operation exceeded time limit

DTS-RETRY-ERR-0312: The table does not comply with the requirements by an external plugin

Possible cause: An external plugin is preventing write operations on the destination database.

Solution: Troubleshoot the database plugin based on the error message. After the issue is resolved, restart the task.

Error example:

DTS-100047: retry 3957 times, 43202 seconds, which exceed the supposed 43200 seconds cause: CriticalAnyAllException: framework: DTS-30011: currentRunningSQL: **** reason: The table does not comply with the requirements by an external plugin. BatchUpdateException: The table does not comply with the requirements by an external plugin. SQLException: The table does not comply with the requirements by an external plugin.

DTS-RETRY-ERR-0313: The connection has been closed

DTS is unable to connect to the database instance because the database connection was closed.

Review the error message and database logs to identify and resolve the issue. Then, restart the task.

Error example:

DTS-100047: retry 0 times, 953 seconds, which exceed the supposed 600 seconds cause: SQLServerException: SQL Server returned an incomplete response. The connection has been closed.

DTS-RETRY-ERR-0314: Failed to get global lock for table/view

Cause: A table or view could not be created in the destination database.

Solution: Check the status of the destination database and the permissions of the database account. After you resolve the issue, restart the task.

Example error:

DTS-10046: execute sql: CREATE TABLE if not exists **** ENGINE=InnoDB DEFAULT CHARSET=utf8 failed. Create TransactionTable failed. cause: SQLException: Failed to get global lock for table/view 'dts.dts****' on master 1

DTS-RETRY-ERR-0315: Cannot convert NULL value to non-Nullable

Cause: A NULL value is written to a column that has a NOT NULL constraint in the destination database.

Solution: Review the error message and the table schema of the source database. Modify the table schema of the destination database. For example, you can remove the NOT NULL constraint from the column that caused the error. Then, restart the task.

Example error:

DTS-100047: retry 4123 times, 43209 seconds, which exceed the supposed 43200 seconds cause: BatchUpdateException: Code: 349. DB::Exception: Cannot convert NULL value to non-Nullable type: while converting source column alerting_time to destination column alerting_time: while executing 'FUNCTION _CAST****

DTS-RETRY-ERR-0319: Cannot set null to non-nullable column

Cause: This error occurs when a null value is written to a column in the destination database that has a NOT NULL constraint.

Example error:

common: DTS-100047: retry 4306 times, 43201 seconds, which exceed the supposed 43200 seconds cause: SQLException: Cannot set null to non-nullable column #7 ****

DTS-RETRY-ERR-0321: Host (.*)? is not allowed to connect to this MySQL server

Cause: DTS cannot connect to the database.

Solution: Add the IP address CIDR blocks of the DTS servers to the database whitelist. Then, restart the task. For more information about the IP address CIDR blocks, see Add the IP addresses of DTS servers to a whitelist.

Error example:

java.sql.SQLException: null, message from server: "Host '100.104.XX.XX' is not allowed to connect to this MySQL server"

DTS-RETRY-ERR-0322: disk is full

Possible cause: The disk space for the destination database is full.

Solution: You can expand the disk space for the destination database and then restart the task.

Error example:

DTS-10046: execute sql: CREATE TABLE if not exists **** ENGINE=InnoDB DEFAULT CHARSET=utf8 failed. Create TransactionTable failed. cause: SQLException: Create table/tablespace 'dts****' failed, as disk is full

DTS-RETRY-ERR-0325: disperse error for column

Possible cause: Data cannot be written to the destination database because its table schema, such as column types or lengths, is inconsistent with that of the source database.

Solution: Modify the table schema of the destination database to be consistent or compatible with the source database. Use the error message and the source table schema for reference. Then, restart the task.

Error example:

DTS-100047: retry 15 times, 15 seconds, which exceed the supposed 922337203685477**** seconds cause: CriticalAnyAllException: database-framework: DTS-61001: disperse error for column:bo_**** BIGINT nullable as bo_**** of table ****

DTS-RETRY-ERR-0326: Socket is closed

Possible cause: DTS cannot connect to the database instance because the database connection is closed.

Solution: Check the error message and database logs to resolve the issue. Then, restart the task.

Error example:

DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 43200 seconds cause: SQLException: java.lang.reflect.InvocationTargetException InvocationTargetException: null IOException: Socket is closed

DTS-RETRY-ERR-0327: Error while executing user ETL

The extract, transform, and load (ETL) process failed because the data processing statement contains an error.

Solution:

For a synchronization instance, check the error message, correct the data processing statement, and then restart the task. For more information, see Configure ETL for a DTS migration or synchronization task.
For a migration instance, reconfigure the migration task and enter the correct data processing statement.

Example error:

framework: DTS-31009: In process of processing data (recordRange: 273076918923611****) failed cause: FatalAnyAllException: common: DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 43200 seconds CriticalAnyAllException: ETL: DTS--0001: Error while executing user ETL: For input string: ****

DTS-RETRY-ERR-0328: Got error IllegalDataException from storage engine

Possible cause: The destination database is in an abnormal state.

Solution: Ensure the destination database is in a normal state and is accessible. Then, restart the task.

Example error:

DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 43200 seconds cause: BatchUpdateException: Got error IllegalDataException from storage engine. Detailed error: Must not use byte[0] for BINARY/VARBINARY, please use null instead. ****

DTS-RETRY-ERR-0329: Data conversion error converting

This error occurs when the table schema of the destination database is inconsistent with that of the source database. For example, the column types or lengths may differ, which prevents data from being written to the destination database.

Solution: Modify the table schema of the destination database to make it consistent with or compatible with the source database schema. You can use the error message and the source table schema as a reference. Then, restart the task.

Example error:

DTS-31009: In process of processing data (recordRange: 576317120221859****) failed cause: FatalAnyAllException: common: DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 43200 seconds DbException: Data conversion error converting "2024-12-19 00:00:00" [22018-193] JdbcSQLException: Data conversion error converting "2024-12-19 00:00:00" [22018-193] NumberFormatException: For input string: "2024-12-19 00:00:00"

DTS-RETRY-ERR-0330: Error while parsing ETL script

Possible cause: An invalid data processing statement for the extract, transform, and load (ETL) operation causes the ETL task to fail.

Solution:

For a synchronization instance: You can review the error message, correct the data processing statement, and then restart the task. For more information, see Configure ETL for a DTS migration or synchronization task.
For a migration instance: You can reconfigure the migration task and enter the correct data processing statement.

Error example:

ETL: DTS--0001: Error while parsing ETL script You have an error in your ETL syntax; check the etl document for the right syntax to use near ****

DTS-RETRY-ERR-0331: User (.)? already has more than (.)? active connections

Cause: The user has reached the maximum number of active database connections.

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

Example error:

DTS-61015: Create connection failed **** cause: MySQLSyntaxErrorException: User hzdball already has more than 'max_****' active connections

DTS-RETRY-ERR-0332: SocketTimeoutException: Read timed out

Cause: The network connection timed out.

Solution: You can ensure that the source database is in a Normal state and is accessible. Then, restart the task.

Example error:

DTS-31009: In process of processing data (recordRange: 513789742289413****) failed cause: FatalAnyAllException: common: DTS-100047: retry 0 times, 3667 seconds, which exceed the supposed 600 seconds CriticalAnyAllException: framework: DTS-31009: read source data error CommunicationsException: Application was streaming results when the connection failed. Consider raising value of 'net_****' on the server. SocketTimeoutException: Read timed out

DTS-RETRY-ERR-0333: Operation not allowed on closed connection

DTS is unable to connect to the database instance because the database connection was closed.

Review the error message and database logs to resolve the issue. Then, restart the task.

Example error:

DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 43200 seconds cause: SQLException: java.lang.reflect.InvocationTargetException InvocationTargetException: null MySQLNonTransientConnectionException: Operation not allowed on closed connection

DTS-RETRY-ERR-0334: Cannot get geometry object from data you send to the GEOMETRY field

Cause: The data written to the GEOMETRY field cannot be parsed into a geometry object.

Solution: Adjust the data type of the corresponding field in the destination database based on the error message. Then, restart the task.

Example:

DTS-100047: retry 4316 times, 43206 seconds, which exceed the supposed 43200 seconds cause: CriticalAnyAllException: framework: DTS-30011: currentRunningSQL: **** insert ignore into ****,currentRow:null, reason: Data truncation: Cannot get geometry object from data you send to the GEOMETRY field BatchUpdateException: Data truncation: Cannot get geometry object from data you send to the GEOMETRY field MysqlDataTruncation: Data truncation: Cannot get geometry object from data you send to the GEOMETRY field

DTS-RETRY-ERR-0335: Cannot parse (.*)? constant

Possible cause: The table schema of the destination database is inconsistent with the source database, for example, in column type or length. This prevents data from being written to the destination database.

Solution: Modify the table schema of the destination database to be consistent with or compatible with the source database and restart the task.

Error example:

DTS-31009: In process of processing data (recordRange: 436256372039247****) failed cause: FatalAnyAllException: common: DTS-100047: retry 0 times, 1 seconds, which exceed the supposed 43200 seconds DbException: Cannot parse "TIMESTAMP" constant "2024-11-01 00:00" [22007-193] JdbcSQLException: Cannot parse "TIMESTAMP" constant "2024-11-01 00:00" [22007-193] IllegalArgumentException: 2024-11-01 00:00

DTS-RETRY-ERR-0336: column (.*)? partition format function error

This error indicates that a function failed because a field in the destination database has an incorrect data format.

Based on the error message and the source table schema, modify the table schema of the destination database to match or be compatible with the source database. Then, restart the task.

Example error message:

DTS-100047: retry 4222 times, 43200 seconds, which exceed the supposed 43200 seconds cause: RuntimeException: Table **** with columns **** and batch exception is **** column **** partition format function error: date_format(?, %Y%m), value: } BatchUpdateException: **** column **** partition format function error: date_format(?, %Y%m), value: ****

DTS-RETRY-ERR-0338: java.lang.NumberFormatException

Possible cause: The table schema of the destination database is inconsistent with the source database. For example, the column type or length may be different. This inconsistency prevents data from being written to the destination database.

Solution: Modify the table schema of the destination database to make it consistent with or compatible with the source database schema. Use the error message and the source database schema for reference. Then, restart the task.

Error example:

DTS-31009: In process of processing data (recordRange: 40009630192186****) failed cause: FatalAnyAllException: common: DTS-100047: retry 1189 times, 43220 seconds, which exceed the supposed 43200 seconds RuntimeException: java.lang.NumberFormatException: For input string: "****" NumberFormatException: For input string: "****"

DTS-RETRY-ERR-0339: Cannot create a JSON value from a string

Possible cause: string data from the source database cannot be written to a JSON field in the destination database.

Solution: Modify the table schema of the destination database to be consistent with or compatible with the source database. Then, restart the task.

Error example:

DTS-100047: retry 1396 times, 43232 seconds, which exceed the supposed 43200 seconds cause: CriticalAnyAllException: framework: **** MysqlDataTruncation: Data truncation: Cannot create a JSON value from a string with CHARACTER SET 'binary'.

DTS-RETRY-ERR-0340: table engine is (.*)? it is a non-transactional engine

Cause: Data cannot be written to the destination database because the destination table uses a non-transactional storage engine.

Solution: If your business requirements permit, change the storage engine of the destination table to a transactional engine, such as InnoDB. Then, restart the task.

Example:

DTS-30021: Optional[cvte_com_zh].Optional[InfoArticle]'s table engine is [MyISAM], it is a non-transactional engine.

DTS-RETRY-ERR-0341: SSL Connection required, but not supported by server

Possible cause: The source or destination database does not support Secure Sockets Layer (SSL) connections.

Solutions:

Method 1: Enable SSL encryption for the source or destination database.
Method 2: Set Encryption to Non-encrypted to connect the source or destination database to DTS.

Error example:

com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: SSL Connection required, but not supported by server.

DTS-RETRY-ERR-0342: Unsupported encoding

Possible cause: The character sets of the source and destination tables are incompatible. This prevents data from being written to the destination database.

Solution: Modify the character set of the destination table. Then, restart the task.

Error example:

DTS-073602: Record Converter failed for the record of table ****. cause by [Unsupported encoding: utf8mb3] About more information in ****

DTS-RETRY-ERR-0343: PSQLException: ERROR: out of memory

Cause: The destination database is out of memory.

Solution: Upgrade the destination database specifications to increase its memory. Then, restart the task.

Error example:

DTS-31009: In process of processing data (recordRange: 343720457685853****) failed cause: FatalAnyAllException: common: DTS-100047: retry 0 times, 35444 seconds, which exceed the supposed 43200 seconds CriticalAnyAllException: framework: DTS-31009: read source data error PSQLException: ERROR: out of memory Detail: Failed on request of size 131072 in memory context "ExecutorState".

DTS-RETRY-ERR-0344: Writer is closed

Possible cause: Data cannot be written to the destination database.

Solution: Ensure that the incremental change logs of the source database exist, the destination database is running normally, its structure is compatible with the source database, and the account has the required permissions. Then, restart the task.

Error example:

DTS-100047: retry 15 times, 15 seconds, which exceed the supposed 922337203685477**** seconds cause: IOException: Writer is closed.

DTS-RETRY-ERR-0345: User writes blocked

Possible cause: The account used by the task for the destination database does not have write permissions.

Solution: Ensure that the destination database account has sufficient write permissions and is not blocked by the database instance. Then, restart the task.

Error example:

DTS-100047: retry 0 times, 2 seconds, which exceed the supposed 922337203685477**** seconds cause: SQLException: com.mongodb.MongoWriteException: Write operation error on server 10.42.XX.XX:XX. Write error: WriteError{code=371, message='User writes blocked', details={}}. MongoWriteException: Write operation error on server 10.42.XX.XX:XX. Write error: WriteError{code=371, message='User writes blocked', details={}}.

DTS-RETRY-ERR-0346: terminating connection due to out of memory

Possible cause: The connection was terminated because the source or destination database ran out of memory.

Solution: Upgrade the source or destination database to increase its memory. Then, restart the task.

Example error:

DTS-31009: In process of processing data (recordRange: 654419472062768****) failed cause: FatalAnyAllException: common: DTS-100047: retry 0 times, 1774 seconds, which exceed the supposed 43200 seconds CriticalAnyAllException: framework: DTS-31009: read source data error PSQLException: FATAL: terminating connection due to out of memory

DTS-RETRY-ERR-0347: Query exceeded maximum time limit

Cause: The SQL query in the source database timed out.

Solution: You can increase the query timeout in the source database or upgrade the database. Then, restart the task.

Error example:

DTS-31009: In process of processing data (recordRange: 305048960847210****) failed cause: FatalAnyAllException: common: DTS-100047: retry 23 times, 43506 seconds, which exceed the supposed 43200 seconds CriticalAnyAllException: framework: DTS-31009: read source data error SQLException: [32005, 202502060853291921682241170345369****] : Query exceeded maximum time limit of 1800000.00ms

DTS-RETRY-ERR-0348: No memory or reach tenant memory limit

Possible cause: The connection to the source or destination database failed because of an out of memory error.

Solution: Upgrade the source or destination database to increase its memory. Then, restart the task.

Example error message:

jdbc-burst: DTS-61015: Create connection failed (url: 10.29.XX.XX:XX, user: cxmrw) cause: SQLException: No memory or reach tenant memory limit

DTS-RETRY-ERR-0349: The (.)? server is running with the (.)? option so it cannot execute this statement

The database is in a read-only or locked state, which prevents data from being written to the destination database.

Contact the database administrator (DBA) to recover the database. Then, restart the task.

Error example:

DTS-100047: retry 120 times, 1800 seconds, which exceed the supposed 1800 seconds cause: TransactionReplicateException: transaction-replicate: DTS-70003: 6 execute transaction has excess max transaction retry time [64] cause:transaction-replicate: DTS-70004: EXEC statement failed, may try it again RecoverableAnyAllException: transaction-replicate: DTS-70004: EXEC statement failed, may try it again SQLException: ****, error detail message:The MySQL server is running with the LOCK_WRITE option so it cannot execute this statement SQLException: The MySQL server is running with the LOCK_WRITE option so it cannot execute this statement

DTS-RETRY-ERR-0350: replication slot (.)? is active for PID (.)?

Cause: The connection between the source database and DTS is abnormal. This issue may be caused by an unstable network.

Solution: Wait for 5 minutes and then restart the task. If the issue persists, join the DTS Customer Communication DingTalk group (Group ID: 116655009709) for assistance. You can download the DingTalk client.

Error example:

DTS-100047: retry 0 times, 1005 seconds, which exceed the supposed 43200 seconds cause: CriticalAnyAllException: dts-k-src: DTS-52111: Increment Context Is Not Running..: CriticalAnyAllException: postgresql-reader: DTS-52510: Fetch postgresql logical log failed CriticalAnyAllException: postgresql-reader: DTS-52512: postgres open replication steam failed PSQLException: ERROR: replication slot "dts_****" is active for PID 3****

DTS-RETRY-ERR-0352: Column is not allowed to be null

Possible cause: A null value was written to a column with a NOT NULL constraint in the destination database.

Solution: Modify the table schema of the destination database according to the error message and the source database's table schema. For example, you can remove the NOT NULL constraint from the column that caused the error. Then, restart the task.

Error example:

DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 3600 seconds cause: CriticalAnyAllException: full-lindorm: DTS-61010: column is not allowed to be null: ****

DTS-RETRY-ERR-0353: GC lifetime is shorter than transaction duration

DTS fails to read data due to a timeout caused by the garbage collection (GC) mechanism of the source database.

Increase the timeout period for the GC mechanism in the source database. Then, restart the task.

Error example:

DTS-31009: In process of processing data (recordRange: 341070835023137****) failed cause: FatalAnyAllException: common: DTS-100047: retry 0 times, 259404 seconds, which exceed the supposed 43200 seconds CriticalAnyAllException: framework: DTS-31009: read source data error SQLException: GC life time is shorter than transaction duration, transaction starts at ****

DTS-RETRY-ERR-0354: No results were returned by the query

Possible cause: DTS did not retrieve any results from the source database.

Solution: Check the status of the database and the network to ensure that DTS can connect to the source database. Then, restart the task.

Example:

DTS-31007: fetch and merge schemas failed cause: CriticalAnyAllException: full-postgresql: DTS-61006: No results were returned by the query. PSQLException: No results were returned by the query.

DTS-RETRY-ERR-0355: PSQLException: An I/O error occurred while sending to the backend

Cause: DTS cannot connect to the database.

Solution: Check the database status, network, firewall (or security settings), and driver settings. Confirm that DTS can connect to the database, and then restart the task.

Example error message:

DTS-100047: retry 0 times, 1667 seconds, which exceed the supposed 43200 seconds cause: PSQLException: An I/O error occurred while sending to the backend. SocketException: Broken pipe (Write failed)

DTS-RETRY-ERR-0356: NotWritablePrimary

Possible cause: The destination endpoint for the task is not a primary node, which prevents data from being written to the destination database.

Solution: Reconfigure the task and set the destination endpoint to the primary node of the database.

Error example:

DTS-100047: retry 0 times, 1 seconds, which exceed the supposed 922337203685477**** seconds cause: SQLException: com.mongodb.MongoNotPrimaryException: Command failed with error 10107 (NotWritablePrimary): 'not master' on server ****

DTS-RETRY-ERR-0357: already exists with different case

Cause: A data write conflict occurs because the destination instance contains a database with a name that differs only in case.

Solution: If your business requirements permit, clear the destination instance and then restart the task.

Note

For a synchronization instance, you can move the object that caused the error from Selected Objects to Source Objects and submit the changes. Then, use the modify synchronization objects feature to add the object back to Selected Objects and use the object name mapping feature to write the data to a different database in the destination instance. For more information, see Modify synchronization objects and Map schemas, tables, and columns.

Error example:

DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 922337203685477**** seconds cause: SQLException: com.mongodb.MongoWriteException: Write operation error on server 10.46.XX.XX:XX. Write error: WriteError{code=13297, message='db already exists with different case already have: [subway] trying to create [Subway]', details={}}. MongoWriteException: Write operation error on server 10.46.XX.XX:XX.. Write error: WriteError{code=13297, message='db already exists with different case already have: [subway] trying to create [Subway]', details={}}.

DTS-RETRY-ERR-0359: Too many filtered rows

Possible cause: An issue with the data prevents it from being written to the destination SelectDB database.

Solution: Use the ErrorUrl in the error message to identify and resolve the issue. Then, restart the task.If you cannot resolve the issue, use DingTalk (DingTalk client download) to join the DTS Customer Communication DingTalk group (Group ID: 116655009709) for assistance.

Error example:

DTS-100047: retry 2775 times, 43207 seconds, which exceed the supposed 43200 seconds cause: TransactionReplicateException: transaction-replicate: DTS-70003: 2 execute transaction has excess max transaction retry time [64] cause:Failed to stream load data to table: esx_shjydd_com.is_customer_logKey status is fail. Load result: ****

DTS-RETRY-ERR-0360: operation exceeded time limit

Cause: Data Transmission Service (DTS) timed out during a query or write operation.

Solution: Check the status of the MongoDB database instance for issues, such as high load or slow SQL statements. After you resolve the issues, restart the DTS task.

Example:

DTS-31009: In process of processing data (recordRange: 561767791805127****) failed cause: FatalAnyAllException: common: DTS-100047: retry 22 times, 43506 seconds, which exceed the supposed 43200 seconds RuntimeException: com.mongodb.MongoExecutionTimeoutException: Executor error during getMore :: caused by :: operation exceeded time limit MongoExecutionTimeoutException: Executor error during getMore :: caused by :: operation exceeded time limit

DTS-RETRY-ERR-0361: Unknown table

Cause: The target table is missing from the destination database.

Solution: Manually create the missing table in the destination database according to the table schema of the source database. Then, restart the task.

Error example:

DTS-31007: get table **** detail info failed after retrying. cause: FatalAnyAllException: common: DTS-100047: retry 4312 times, 43209 seconds, which exceed the supposed 43200 seconds RecoverableAnyAllException: replicate-selectdb: DTS-70002: get table **** detail info failed. SQLException: errCode = 2, detailMessage = Unknown table ****

DTS-RETRY-ERR-0362: Not support string len over than `string_type_length_soft_limit_bytes`

Cause: The length of the string data exceeds the limit of the destination SelectDB database.

Solution: Increase the value of the string_type_length_soft_limit_bytes parameter in the SelectDB database to accommodate the maximum length of the string data. Then, restart the task.

Error example:

DTS-100047: retry 52 times, 602 seconds, which exceed the supposed 600 seconds cause: IOException: Failed to stream load data to SelectDB.Key status is fail. Load result: **** add batch req success but status isn't ok, err: [E-1201]PStatus: (172.16.XX.XX)[E-1201]failed to append block: [NOT_IMPLEMENTED_ERROR]Not support string len over than `string_type_length_soft_limit_bytes` in vec engine., ****

DTS-RETRY-ERR-0363: Can't get text on a START_OBJECT

Cause: The structure of the destination Elasticsearch database is abnormal.

Solution: Change the type of the corresponding field in the destination index to Object. Then, restart the task.

Error example:

DTS-100047: retry 15 times, 28 seconds, which exceed the supposed 922337203685477**** seconds cause: IOException: es: DTS-10035: failed to parse field **** of type [text] in document with id '13312'. Preview of field's value: '****', Can't get text on a START_OBJECT at 1:2380 CriticalAnyAllException: es: DTS-10035: failed to parse field **** of type [text] in document with id '13312'. Preview of field's value: '****', Can't get text on a START_OBJECT at 1:2380

DTS-RETRY-ERR-0364: No such index

Possible cause: The required index is missing from the destination Elasticsearch database.

Solution: Create the missing index in the destination Elasticsearch database based on the error message, and then restart the task.

Error example:

DTS-100047: retry 15 times, 25 seconds, which exceed the supposed 922337203685477**** seconds cause: IOException: es: DTS-10035: no such index **** and **** contains [-*] which forbids automatic creation of the index CriticalAnyAllException: es: DTS-10035: no such index **** and **** contains [-*] which forbids automatic creation of the index

DTS-RETRY-ERR-0365: index read-only

Possible cause: The destination Elasticsearch index is in read-only mode, which prevents data from being written to it.

Solution: Set the destination Elasticsearch index to read/write mode, and then restart the task.

Error example:

DTS-100047: retry 15 times, 57 seconds, which exceed the supposed 922337203685477**** seconds cause: IOException: es: DTS-10035: blocked by: [FORBIDDEN/12/index read-only / allow delete (api)]; CriticalAnyAllException: es: DTS-10035: blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];

DTS-RETRY-ERR-0366: unable to authenticate user

Possible cause: The account or password for the destination Elasticsearch database is incorrect.

Solution:

Incorrect password: Go to the Basic Information page of the DTS instance. In the Destination section, click Change Password. Enter the correct password for the destination Elasticsearch database and restart the task.
Incorrect database account: Reconfigure the DTS task with the correct database account and password.

Error example:

unable to authenticate user [elastic]

DTS-RETRY-ERR-0367: in encoding "UTF8" has no equivalent in encoding "GBK" (.*)?

Cause: Data cannot be written to the destination database because the character sets of the source and destination database tables are incompatible.

Solution: Change the character set of the destination database table to a compatible one, such as GB18030. Then, restart the task.

Example:

DTS-100047: retry 4037 times, 43208 seconds, which exceed the supposed 43200 seconds cause: CriticalAnyAllException: framework: DTS-30011: currentRunningSQL: **** on conflict do nothing was aborted: ERROR: character with byte sequence 0xee 0x96 0x83 in encoding "UTF8" has no equivalent in encoding "GBK" Where: unnamed portal parameter $12 Call getNextException to see other errors in the batch. PSQLException: ERROR: character with byte sequence 0xee 0x96 0x83 in encoding "UTF8" has no equivalent in encoding "GBK" Where: unnamed portal parameter $12

DTS-RETRY-ERR-0368: alter table (.)? canceling statement due to user request (.)?

Possible cause: The DTS instance failed to initialize.

Solution: You can restart the task during off-peak hours, such as when the CPU load of the source and destination databases is below 30 %.

Error example:

DTS-52110: PostgresRecordExtractor Init Error: postgresql-reader: DTS-52511: alter replica identity thread exception, readerContext=ReaderContext [****] cause: CriticalAnyAllException: postgresql-reader: DTS-52511: alter replica identity thread exception ExecutionException: postgresql-reader: DTS--0001: alter table identity: ****/d failed, case by common: DTS-100047: retry 0 times, 300019 seconds, which exceed the supposed 43200 seconds cause: FatalAnyAllException: common: DTS-100047: retry 0 times, 300019 seconds, which exceed the supposed 43200 seconds PSQLException: ERROR: canceling statement due to user request CriticalAnyAllException: postgresql-reader: DTS--0001: alter table identity: ****/d failed, case by common: DTS-100047: retry 0 times, 300019 seconds, which exceed the supposed 43200 seconds FatalAnyAllException: common: DTS-100047: retry 0 times, 300019 seconds, which exceed the supposed 43200 seconds PSQLException: ERROR: canceling statement due to user request

DTS-RETRY-ERR-0369: requested WAL segment (.*)? has already been removed

Possible cause: The Write-Ahead Logging (WAL) files were removed from the source database.

Solution: Contact the source database administrator (DBA) to resolve the issue. Then, restart the task.

Error example:

DTS-100047: retry 0 times, 1000 seconds, which exceed the supposed 43200 seconds cause: CriticalAnyAllException: dts-k-src: DTS-52111: Increment Context Is Not Running..: CriticalAnyAllException: postgresql-reader: DTS-52510: Fetch postgresql logical log failed IOException: org.postgresql.util.PSQLException: ERROR: requested WAL segment 00000002000000F000000013 has already been removed PSQLException: ERROR: requested WAL segment 00000002000000F000000013 has already been removed

DTS-RETRY-ERR-0370: Password authentication failed for user (.*)?

Possible cause: The task cannot connect to the database because the database account or password configured for the task is incorrect.

Solution:

Incorrect database password: Go to the Basic Information page of the DTS instance in the DTS console. In the Destination section, click Change Password. Enter the correct database password, and then restart the task.
Incorrect database account: Reconfigure the DTS task with the correct database account and password.

Error example:

DTS-100047: retry 1 times, 44134 seconds, which exceed the supposed 43200 seconds cause: PSQLException: FATAL: password authentication failed for user ****

DTS-RETRY-ERR-0371: must be owner of table (.*)?

Cause: The database account specified for the task does not have the required owner permission.

Solution: Grant the required permissions to the database account and restart the task. Alternatively, you can reconfigure the task to use a database account that has the required permissions.

Error example:

DTS-52110: PostgresRecordExtractor Init Error: postgresql-reader: DTS-52511: alter replica identity thread exception, readerContext=ReaderContext [****] cause: CriticalAnyAllException: postgresql-reader: DTS-52511: alter replica identity thread exception ExecutionException: postgresql-reader: DTS--0001: alter table identity: ****/d failed, case by common: DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 43200 seconds cause: FatalAnyAllException: common: DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 43200 seconds PSQLException: ERROR: must be owner of table **** CriticalAnyAllException: postgresql-reader: ****

DTS-RETRY-ERR-0372: jdbc-burst (.)? Create connection failed (.)?

Cause: The connection to the database instance failed.

Solution: Verify the database connection details, and then restart the task.

Error example:

DTS-100047: retry 1 times, 45377 seconds, which exceed the supposed 43200 seconds cause: DBCommonException: jdbc-burst: DTS-61015: Create connection failed (url: ****, user: ****) PSQLException: The connection attempt failed. EOFException: null

DTS-RETRY-ERR-0373: create publication error for (.*)? PSQLException: ERROR: operation is not allowed on this node Hint: Connect to the coordinator and run it again.

This error occurs when the source or destination database is a PolarDB for PostgreSQL Distributed Edition cluster.

Solution: DTS does not currently support PolarDB for PostgreSQL Distributed Edition clusters.

Example:

DTS-100047: retry 0 times, 1001 seconds, which exceed the supposed 43200 seconds cause: CriticalAnyAllException: dts-k-src: DTS-52111: Increment Context Is Not Running..: CriticalAnyAllException: postgresql-reader: DTS-52510: Fetch postgresql logical log failed CriticalAnyAllException: postgresql-reader: DTS-52514: create publication error for **** PSQLException: ERROR: operation is not allowed on this node Hint: Connect to the coordinator and run it again.

DTS-RETRY-ERR-0374: postgres logical log not find (.*)?

Cause: DTS cannot find data at the specified offset in the source database.

Solution: You can reconfigure the task.

Error example:

DTS-100047: retry 0 times, 1001 seconds, which exceed the supposed 600 seconds cause: CriticalAnyAllException: dts-k-src: DTS-52111: Increment Context Is Not Running..: CriticalAnyAllException: postgresql-reader: DTS-52510: Fetch postgresql logical log failed CriticalAnyAllException: postgresql-reader: DTS-52511: postgres logical log not find

DTS-RETRY-ERR-0375: FATAL: terminating connection due to out of memory (.*)?

Cause: The database ran out of memory (OOM).

Solution: Contact the database administrator (DBA) to resolve the issue. Then, restart the job.

Error example:

DTS-52111: Increment Context Is Not Running..: cause: CriticalAnyAllException: postgresql-reader: DTS-52510: Fetch postgresql logical log failed CriticalAnyAllException: postgresql-reader: DTS--0001: execute sql select **** failed, case by common: DTS-100047: retry 0 times, 401 seconds, which exceed the supposed 43200 seconds FatalAnyAllException: common: DTS-100047: retry 0 times, 401 seconds, which exceed the supposed 43200 seconds PSQLException: FATAL: terminating connection due to out of memory

DTS-RETRY-ERR-0376: function dt_sub is not supported, maybe is op_sub (.*)?

Possible cause: The extract, transform, and load (ETL) process failed because the data processing statement is incorrect.

Solution:

For a synchronization instance: Check and correct the data processing statement based on the error message. Then, restart the task. For more information, see Configure ETL for a DTS migration or synchronization task.
For a migration instance: Reconfigure the migration task and enter the correct data processing statement.

Error example:

DTS--0001: Error while parsing ETL script function dt_sub is not supported, maybe is op_sub cause: ParseException: function dt_sub is not supported, maybe is op_sub

DTS-RETRY-ERR-0378: An I/O error occurred while sending to the backend (.*)?

Cause: Data cannot be written to the destination database because the network connection between Data Transmission Service (DTS) and the destination database has timed out.

Solution: Ensure the destination database is running and accessible. Then, restart the task.

Example error:

DTS-100047: retry 11 times, 43315 seconds, which exceed the supposed 43200 seconds cause: CriticalAnyAllException: framework: DTS-30011: currentRunningSQL: **** on conflict do nothing was aborted: An I/O error occurred while sending to the backend. Call getNextException to see other errors in the batch. BatchUpdateException: Batch entry 0 **** on conflict do nothing was aborted: An I/O error occurred while sending to the backend. Call getNextException to see other errors in the batch. PSQLException: An I/O error occurred while sending to the backend. SocketTimeoutException: Read timed out

DTS-RETRY-ERR-0379: deadlock detected (.*)?

Possible cause: The DTS instance failed to initialize.

Solution: Restart the task during off-peak hours, when the CPU load on the source and destination databases is below 30%.

Error example:

DTS-52110: PostgresRecordExtractor Init Error: postgresql-reader: DTS-52511: alter replica identity thread exception, readerContext=ReaderContext **** cause: CriticalAnyAllException: postgresql-reader: DTS-52511: alter replica identity thread exception ExecutionException: postgresql-reader: DTS--0001: alter table identity: **** failed, case by common: DTS-100047: retry 0 times, 2003 seconds, which exceed the supposed 43200 seconds FatalAnyAllException: common: DTS-100047: retry 0 times, 2003 seconds, which exceed the supposed 43200 seconds PSQLException: ERROR: deadlock detected Detail: Process 18023 waits for AccessShareLock on relation 122000 of database 16392; blocked by process 18028. Process 18028 waits for AccessExclusiveLock on relation 121960 of database 16392; blocked by process 18023. Hint: See server log for query details.

DTS-RETRY-ERR-0380: index row size (.)? exceeds maximum (.)? for index (.*)?

Possible cause: The table schema of the destination database is inconsistent with the source database. The length of an index exceeds the limit of the destination database, which prevents data from being written.

Solution: Modify the table schema of the destination database to be consistent or compatible with the source database. Refer to the error message and the source table schema. Then, restart the task.

Error example:

DTS-100047: retry 3798 times, 43209 seconds, which exceed the supposed 43200 seconds cause: CriticalAnyAllException: framework: DTS-30011: currentRunningSQL: **** on conflict do nothing was aborted: ERROR: index row size 3368 exceeds maximum 2712 for index "company_recommend_t****" Call getNextException to see other errors in the batch. BatchUpdateException: Batch entry 0 **** values **** on conflict do nothing was aborted: ERROR: index row size 3368 exceeds maximum 2712 for index "company_recommend_t****" Call getNextException to see other errors in the batch. PSQLException: ERROR: index row size 3368 exceeds maximum 2712 for index "company_recommend_t****"

DTS-RETRY-ERR-0381: canceling statement due to statement timeout (.*)?

Possible cause: The DTS instance failed to initialize.

Solution: You can restart the task during off-peak hours, such as when the CPU load of the source and destination databases is below 30%.

Error example:

DTS-52110: PostgresRecordExtractor Init Error: postgresql-reader: DTS-52511: alter replica identity thread exception, readerContext=ReaderContext **** cause: CriticalAnyAllException: postgresql-reader: DTS-52511: alter replica identity thread exception ExecutionException: postgresql-reader: DTS--0001: alter table identity: ****/d failed, case by common: DTS-100047: retry 0 times, 59975 seconds, which exceed the supposed 43200 seconds cause: FatalAnyAllException: common: DTS-100047: retry 0 times, 59975 seconds, which exceed the supposed 43200 seconds PSQLException: ERROR: canceling statement due to statement timeout CriticalAnyAllException: postgresql-reader: DTS--0001: alter table identity: ****/d failed, case by common: DTS-100047: retry 0 times, 59975 seconds, which exceed the supposed 43200 seconds FatalAnyAllException: common: DTS-100047: retry 0 times, 59975 seconds, which exceed the supposed 43200 seconds PSQLException: ERROR: canceling statement due to statement timeout

DTS-RETRY-ERR-0382: violates foreign key constraint (.*)?

Possible cause: The source data contains foreign keys, and the account used for the destination database is not a privileged account or an account with superuser permissions.

Solution: In the destination database, manually set the session_replication_role parameter to replica. Then, restart the task. After the DTS task is complete or released, change the session_replication_role parameter back to origin.

Note

If this parameter is not set, data inconsistency may occur in specific scenarios, such as when the destination database uses cascade updates, cascade deletes, or triggers.

Error example:

DTS-100047: retry 717 times, 7200 seconds, which exceed the supposed 7200 seconds cause: CriticalAnyAllException: framework: DTS-30011: currentRunningSQL: **** on conflict do nothing was aborted: ERROR: insert or update on table **** violates foreign key constraint **** is not present in table ****. Call getNextException to see other errors in the batch. BatchUpdateException: Batch entry 0 **** on conflict do nothing was aborted: ERROR: insert or update on table **** violates foreign key constraint **** is not present in table ****. Call getNextException to see other errors in the batch. PSQLException: ERROR: insert or update on table **** violates foreign key constraint **** is not present in table ****

DTS-RETRY-ERR-0383: value too long for type (.*)?

Possible cause: The table schema of the destination database is inconsistent with that of the source database. For example, a column's type or length may be different, which prevents data from being written to the destination database.

Solution: Modify the table schema of the destination database to be consistent with or compatible with the source database. You can use the error message and the source database's table schema for reference. Then, restart the task.

Error example:

DTS-100047: retry 4297 times, 43200 seconds, which exceed the supposed 43200 seconds cause: CriticalAnyAllException: framework: DTS-30011: currentRunningSQL: **** on conflict do nothing,currentRow **** on conflict do nothing was aborted: ERROR: value too long for type character varying(17) Call getNextException to see other errors in the batch. BatchUpdateException: Batch entry 0 **** on conflict do nothing was aborted: ERROR: value too long for type character varying(17) Call getNextException to see other errors in the batch. PSQLException: ERROR: value too long for type character varying(17)

DTS-RETRY-ERR-0384: Function "TIMESTAMP" not found (.*)?

Cause: The filter condition for the task specifies an object that does not exist in the source database.

Solution:

For a sync task: Modify the Filter Conditions. For more information, see What to do next.
For a migration task: Reconfigure the task and use the correct filter condition.

Error example:

DTS-31009: In process of processing data (recordRange: 247513824836871****) failed cause: FatalAnyAllException: common: DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 43200 seconds DbException: Function "TIMESTAMP" not found [90022-193] JdbcSQLException: Function "TIMESTAMP" not found [90022-193]

DTS-RETRY-ERR-0385: Could not find a server with specified targetServerType: primary (.*)?

Possible cause: Data cannot be written to the destination database because a primary/standby switch has occurred.

Solution: Contact the database administrator (DBA) to resolve the issue. Then, restart the task.

Error example:

DTS-100047: retry 1 times, 43335 seconds, which exceed the supposed 43200 seconds cause: DBCommonException: jdbc-burst: DTS-61015: Create connection failed **** PSQLException: Could not find a server with specified targetServerType: primary

DTS-RETRY-ERR-0386: syntax error at or near (.*)? alter table identity

Possible cause: A table name in the source or destination database contains special characters.

Solution: You can use DingTalk (Download the DingTalk client) to join the DTS Customer Communication DingTalk group (Group ID: 116655009709) for assistance.

Error example:

DTS-52110: PostgresRecordExtractor Init Error: postgresql-reader: DTS-52511: alter replica identity thread exception, readerContext=ReaderContext**** cause: CriticalAnyAllException: postgresql-reader: DTS-52511: alter replica identity thread exception ExecutionException: postgresql-reader: DTS-00035: alter table identity: ****/d failed, case by common: DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 43200 seconds cause: FatalAnyAllException: common: DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 43200 seconds PSQLException: ERROR: syntax error at or near **** Position: 35 CriticalAnyAllException: postgresql-reader: DTS-00035: alter table identity: ****/d failed, case by common: DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 43200 seconds FatalAnyAllException: common: DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 43200 seconds PSQLException: ERROR: syntax error at or near ****

DTS-RETRY-ERR-0387: terminating connection due to administrator command (.*)?

Possible cause: The connection between DTS and the database is disconnected.

Solution: You can reconfigure the task.

Example of an error:

DTS-52111: Increment Context Is Not Running..: cause: CriticalAnyAllException: postgresql-reader: DTS-52510: Fetch postgresql logical log failed CriticalAnyAllException: postgresql-reader: DTS-52514: create publication error for dts_sync_**** CriticalAnyAllException: postgresql-reader: DTS--0001: execute sql select prrelid from pg_public**** where prpubid = 6543770; failed, case by common: DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 43200 seconds FatalAnyAllException: common: DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 43200 seconds PSQLException: FATAL: terminating connection due to administrator command

DTS-RETRY-ERR-0388: index row size (.)? exceeds btree version (.)? maximum (.*)? for index

Possible cause: The table schema of the destination database is inconsistent with the source database. As a result, the length of an index exceeds the limit of the destination database, preventing data from being written.

Solution: Modify the table schema of the destination database to be consistent or compatible with the source schema. Use the error message and the source schema for reference. Then, restart the task.

Error example:

DTS-100047: retry 4252 times, 43206 seconds, which exceed the supposed 43200 seconds cause: CriticalAnyAllException: framework: DTS-30011: currentRunningSQL: **** on conflict do nothing was aborted: ERROR: index row size 2808 exceeds btree version 4 maximum 2704 for index **** Detail: Index row references tuple (7968098,6) in relation ****. Hint: Values larger than 1/3 of a buffer page cannot be indexed. Consider a function index of an MD5 hash of the value, or use full text indexing. Call getNextException to see other errors in the batch. BatchUpdateException: Batch entry 0 **** on conflict do nothing was aborted: ERROR: index row size 2808 exceeds btree version 4 maximum 2704 for index ****" Detail: Index row references tuple (7968098,6) in relation ****. Hint: Values larger than 1/3 of a buffer page cannot be indexed. Consider a function index of an MD5 hash of the value, or use full text indexing. Call getNextException to see other errors in the batch. PSQLException: ERROR: index row size 2808 exceeds btree version 4 maximum 2704 for index **** Detail: Index row references tuple (7968098,6) in relation ****. Hint: Values larger than 1/3 of a buffer page cannot be indexed. Consider a function index of an MD5 hash of the value, or use full text indexing.

Other common errors

DTS-10015

Description: Failed to connect to Redis.

Possible cause: An issue with the Redis server is preventing a connection.

Solution: Check the status of the Redis server, resolve any issues, and then verify the connection.

Example of an error:

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

Description: An SQL statement failed to execute.

Possible cause: The database account does not have the CREATE TABLE permission.

Solution: Grant the required permissions to the database account.

Note

This error code is usually accompanied by a more specific database error message. Refer to that message to check and correct the SQL statement.

Incorrect example:

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

Description: Failed to save metadata.

Possible cause: The source database contains tables with the same name but different capitalization, such as TABLE and table. DTS does not support this scenario.

Solution: Check the source database and your business logic. Rename one of the conflicting tables, and then recreate the job.

Example:

DTS-30005: save changed job progress info failed cause: SQLException:result content unexpected. expect 3 time 1, actually [2, 1, 1]

DTS-30011

Error description: An error occurred while writing data.

Possible cause 1:

The disk space is full.
The table size has reached its limit.

Solution 1:

Scale out the disk space and restart the task.
Resolve the table size limit at the database level and restart the task.
Note
For more information about table size limits in MySQL databases, see B.3.2.10 The table is full.

Error example 1:

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 occurred in the destination database.

Solution 2: If the destination database is a MySQL database, run the following commands to check for locks.

SHOW FULL PROCESSLIST;
SELECT
* FROM innodb_trx;

Note

After you resolve the issue, restart the task.

Error example 2:

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 read-only.

Solution 3:

Run the SELECT @@read_only; statement to check whether the destination database is in read-only mode.
Run the SET GLOBAL read_only=0; statement to disable read-only mode.

Note

After you disable read-only mode, restart the task.

Error example 3:

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

Error message: The column does not exist.

Possible causes

You did not select schema migration during task configuration. This causes the table schemas of the source and destination databases to be inconsistent.
You executed Data Definition Language (DDL) statements on the source or destination database after the task was configured. This action modified the table schema and caused an inconsistency.

Adjust the table schemas of the source and destination databases to ensure they are consistent.

Note

If the reasons above do not apply to your situation, try the following methods:

Restart the task to see if it resumes.
Remove the table that is causing the error from the synchronization objects and then add it back. Check if the task resumes.

Error example

DTS-30018: Can not find column [column_in_source<-->column_in_target] in target table db_name.table_name

DTS-30019

Error message: The column does not exist.

Possible causes

You did not select schema migration during task configuration. This causes the table schemas of the source and destination databases to be inconsistent.
You executed Data Definition Language (DDL) statements on the source or destination database after the task was configured. This action modified the table schema and caused an inconsistency.

Adjust the table schemas of the source and destination databases to ensure they are consistent.

Note

If the reasons above do not apply to your situation, try the following methods:

Restart the task to see if it resumes.
Remove the table that is causing the error from the synchronization objects and then add it back. Check if the task resumes.

Error example:

DTS-30019: Cannot find column [column_in_source<-->column_in_target] in target table db_name.table_name

DTS-30020

Description: An SQL statement failed to execute.

Possible cause: The database account does not have the CREATE TABLE permission.

Solution: Grant the required permissions to the database account.

Note

This error code is usually accompanied by a more specific database error message. Refer to that message to check and correct the SQL statement.

Example error:

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

Error description: The DTS writer module cannot read data from the DTS cache module for a specific point in time.

Cause 1: The task was paused for an extended period. When the task is restarted, the data for the corresponding offset (2021-5-20 21:17:51) no longer exists in the DTS cache module.

Note

The time in the error message is a UNIX timestamp. You can use a search engine to find a UNIX timestamp converter and convert the timestamp to UTC.

Solution 1:

Method 1: Check the logs in the source database that are used for incremental data parsing, such as binary logging (Binlog) or Redolog. Verify that the time range of the logs includes this point in time. If it does, use DingTalk (Download DingTalk client) to join the DTS Customer Communication DingTalk group (ID: 116655009709) and request assistance.
Method 2: Create the task again. When you run the task, avoid pausing it for an extended period. A task cannot be restarted if it has been paused for more than 6 hours.

Cause 2: The task remained in a failed state for an extended period. After the issue is resolved and the task is resumed, the data for the corresponding offset no longer exists in the DTS cache module.

Solution 2: Create the task again. If an error occurs while the task is running, resolve the issue and resume the task as soon as possible. This prevents the task from becoming unrecoverable, which can occur if it remains in a failed state for an extended period.

Cause 3: During a full migration or full sync, DTS locally caches data logs from the source database. The cache stores logs from the last 24 hours or up to 50 GB of data in a loop. These logs are used for incremental data parsing. If the full migration or full sync takes a long time, DTS may have purged the cached data logs that were generated after the task started. This results in incomplete data logs for incremental parsing.

Solution 3: Create the task again. Before you create the task, estimate the data volume for the migration or synchronization. If the data volume is large, split the data across multiple migration or sync tasks.

Error example:

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

The DTS writer module timed out when reading from the DTS cache module.

Possible cause: The connection from the data writing module to the cache module timed out due to issues such as network jitter.

You can restart the task and check if it runs normally.

Example error:

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

Description: Cannot connect to the source database.

Possible cause: The username or password is incorrect.

Solution: Enter the correct username and password, and restart the task.

Note

If none of the reasons listed above apply, try the following methods:

Check the status of the source database.
Check if the account password was changed.
Check if all required IP addresses are added to the whitelist. For more information, see IP whitelists for on-premises databases.
Check if the number of connections to the source database exceeds the limit.

Example of an error:

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

Error description: A connection to the source database failed.

Possible cause: The source database has too many connections.

Resolution: Check the database's maximum connection limit and the number of active connections. If necessary, adjust the max_connections parameter and restart the task.

Error example:

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

Description: The connection to the database failed, or the specified database or table does not exist.

Possible cause: The table was not migrated to the destination database due to a schema migration error. The table schema was also not manually created in the destination database.

Solution: Check the error message to verify that the database or table exists. If it does not exist:

For a sync task: Remove the table that caused the error from the sync objects. Then, add the table again and check whether the task can be restored.
The migration task rebuilds the link.

Error example:

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

Error: SQL execution failed.

Note

This error message typically appears when the destination database is AnalyticDB for MySQL.

Possible cause 1: The DDL operation failed because the data synchronization channel does not support this type of operation.

Solution 1:

For synchronization of specific tables: You can resynchronize the table. To do this, remove the table from the synchronization objects, delete it from the destination database, and then add it back. DTS then performs a full data synchronization that includes a schema pull, which bypasses this type of DDL operation.
For full database synchronization: In AnalyticDB for MySQL, you can create a new table with a different name but a schema that matches the source table. Use the INSERT INTO SELECT statement to copy the data from the source table to the new table. Delete the original table that caused the error. Use the RENAME statement to rename the new table to the original name. Then, restart the task.

Example error 1:

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: A SHUTDOWN operation was executed on the destination database.

Solution 2: You can confirm that the destination database is running normally, and then restart the task.

Example error 2:

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: A network or account permission issue occurred. For example, the account is not permitted to remotely log on to the AnalyticDB for MySQL database.

Solution 3:

You can check whether all required IP addresses are added to the whitelist. For more information, see Add the CIDR blocks of DTS servers to the IP address whitelist of a database.
You can check whether the account has remote logon permissions.

Note

After you resolve the issue, you can restart the task.

Example error 3:

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 table does not exist.

Solution 4:

You can check whether the table was deleted from the destination database.
You can check whether the table schema was synchronized or migrated to the destination database.

Note

After you resolve the issue, you can restart the task.

Example error 4:

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: A database integrity constraint was violated. For example, a NULL value was inserted into a column that does not allow NULL values.

Solution 5: You can check the table schema and the records affected by the DML statement. Ensure that the source and destination table schemas are identical. Alternatively, you can correct the data and then restart the task.

Example error 5:

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 destination database account has insufficient permissions.

Solution 6: You can check whether the destination database account has the permissions specified in the error message. If not, grant the required permissions and then restart the task.

Example error 6:

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

Error message: The column does not exist.

Possible causes

You did not select schema migration during task configuration. This causes the table schemas of the source and destination databases to be inconsistent.
You executed Data Definition Language (DDL) statements on the source or destination database after the task was configured. This action modified the table schema and caused an inconsistency.

Adjust the table schemas of the source and destination databases to ensure they are consistent.

Note

If the reasons above do not apply to your situation, try the following methods:

Restart the task to see if it resumes.
Remove the table that is causing the error from the synchronization objects and then add it back. Check if the task resumes.

Example error:

DTS-70019: Can not find column [column_in_source<-->column_in_target] in target table db_name.table_name

DTS-71016

Error message: Cannot connect to the destination database.

Cause 1: The destination database has reached its connection limit.

Solution 1: You can increase the maximum connections for the destination database and then restart the task.

Error example 1:

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"

Cause 2: Connections are blocked because of too many failed database connection attempts from the same IP address within a short period.

Solution 2: You can resolve this issue on the destination database, such as by increasing the value of MAX_CONNECTION_ERRORS. Then, restart the task.

Error example 2:

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

Error description: DTS failed to parse MySQL binary logs.

Possible cause: The table schema in the binary log is inconsistent with the schema that DTS stores locally, which causes parsing to fail. This inconsistency occurs when a Data Definition Language (DDL) statement that changes the table schema is not recorded in the binary log. As a result, DTS cannot parse the DDL statement and does not update its local schema. For example, running the SET SESSION sql_log_bin=0 statement before changing a field type from INT(11) to BIGINT(20) causes this issue.

Solution: Reload the table schema from the DTS local storage.For assistance, use DingTalk (Download DingTalk) to join the DTS customer communication DingTalk group (Group ID: 116655009709).

Error example:

java.IOEException: java.lang.IllegalArgumentException: Valid type fail, Column:column_name,Type:type_number

DTS-100047

Description: The DTS connection to the database instance timed out.

Possible cause: The timeout parameters for the database instance are set too low.

Solution: You can increase the values of the net_read_timeout and net_write_timeout parameters. Then, restart the task.

Error example:

****
FatalAnyAllException:common:DTS-100047:retry0times,4791628seconds,whichexceedthesupposed600seconds
CriticalAnyAllException:framework:DTS-31009:readsourcedataerror
****