DTS-RETRY-ERR-0301 to 0400

DTS-RETRY-ERR-0301: Invalid character data was found

Possible cause: The destination database or table uses a character set incompatible with the source, preventing data from being written.

Solution: Change the character set of the destination database or table to one compatible with the source, then restart the DTS task.

Sample error message:

truncated CriticalAnyAllException: postgresql: DTS-11002: Invalid character data was found.

DTS-RETRY-ERR-0302: (.*)? is none in where causes

Possible cause: The filter conditions configured in the DTS instance are incorrect.

Solution:

• Sync instance: Correct the filter clauses, then restart the DTS task. For more information, see What to do next.

• Migration instance: Restart the DTS task. If the instance cannot be recovered, reconfigure the DTS task.

Sample error message:

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 length of some columns in the data to be written exceeds the maximum length of those columns in the destination database.

Solution: Modify the maximum length of the problematic column in the destination database table to meet the data writing requirements, then restart the DTS task.

Sample error message:

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 extract, transform, and load (ETL) data processing statement is incorrect, causing ETL execution to fail.

Solution:

• Sync instance: Check and correct the data processing statement, then restart the DTS task.

• Migration instance: Reconfigure the migration task with the correct data processing statement.

Sample error message:

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: Verify that incremental change logs exist in the source database, the destination database is running normally, the destination database schema is compatible with the source, and the destination database account has the required permissions. Then restart the DTS task.

Sample error message:

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 ETL data processing statement is incorrect, causing ETL execution to fail.

Solution:

• Sync instance: Check and correct the data processing statement, then restart the DTS task.

• Migration instance: Reconfigure the migration task with the correct data processing statement.

Sample error message:

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

Sample error message:

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

Possible cause: DTS timed out when executing change operations in the destination MongoDB database.

Solution: If your business allows, remove the database timeout limit or upgrade the database specifications, then restart the DTS task.

Sample error message:

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: The destination database cannot perform write operations due to external plugin restrictions.

Solution: Troubleshoot and resolve the database plugin issues, then restart the DTS task.

Sample error message:

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

Possible cause: The database connection has been closed, preventing DTS from connecting to the database instance.

Solution: Check the database logs to identify the root cause, resolve the issue, then restart the DTS task.

Sample error message:

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

Possible cause: Cannot create tables or views in the destination database.

Solution: Troubleshoot issues related to the database status and database account permissions, then restart the DTS task.

Sample error message:

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

Possible cause: Null values are being written to columns with NOT NULL constraints in the destination database.

Solution: Check the error message and the source database schema, then modify the destination database schema accordingly (for example, remove the NOT NULL constraint from the problematic column). Restart the DTS task.

Sample error message:

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

Possible cause: Null values are being written to columns with NOT NULL constraints in the destination database.

Solution: Check the error message and the source database schema, then modify the destination database schema accordingly (for example, remove the NOT NULL constraint from the problematic column). Restart the DTS task.

Sample error message:

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

Possible cause: DTS cannot connect to the database.

Solution: Troubleshoot database whitelist issues and add the DTS server IP address ranges to the database security settings. Then restart the DTS task.

Sample error message:

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 destination database disk is full.

Solution: Expand the disk space of the destination database, then restart the DTS task.

Sample error message:

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: The destination database schema (such as column types or lengths) is inconsistent with the source, preventing data from being written.

Solution: Check the error message and the source database schema, then modify the destination database schema to be consistent with (or compatible with) the source. Restart the DTS task.

Sample error message:

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: The database connection has been closed, preventing DTS from connecting to the database instance.

Solution: Check the database logs to identify the root cause, resolve the issue, then restart the DTS task.

Sample error message:

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

Possible cause: The ETL data processing statement is incorrect, causing ETL execution to fail.

Solution:

• Sync instance: Check and correct the data processing statement, then restart the DTS task.

• Migration instance: Reconfigure the migration task with the correct data processing statement.

Sample error message:

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

Solution: Verify that the destination database is running normally and can be connected, then restart the DTS task.

Sample error message:

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

Possible cause: The destination database schema (such as column types or lengths) is inconsistent with the source, preventing data from being written.

Solution: Check the error message and the source database schema, then modify the destination database schema to be consistent with (or compatible with) the source. Restart the DTS task.

Sample error message:

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: The ETL data processing statement is incorrect, causing ETL execution to fail.

Solution:

• Sync instance: Check and correct the data processing statement, then restart the DTS task.

• Migration instance: Reconfigure the migration task with the correct data processing statement.

Sample error message:

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

Possible cause: The database connection limit has been reached.

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

Sample error message:

DTS-61015: Create connection failed **** cause: MySQLSyntaxErrorException: User hzdball already has more than 'max_****' active connections

DTS-RETRY-ERR-0332: SocketTimeoutException: Read timed out

Possible cause: Network communication between DTS and the database timed out.

Solution: Verify that the source database is running normally and DTS can connect to it (check the database connection settings, whitelist settings, and account credentials). Then restart the DTS task.

Sample error message:

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

Possible cause: The database connection has been closed, preventing DTS from connecting to the database instance.

Solution: Check the database logs to identify the root cause, resolve the issue, then restart the DTS task.

Sample error message:

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

Possible cause: The data being written to the GEOMETRY type field cannot be parsed as a geometry object.

Solution: Adjust the type of the corresponding field in the destination database, then restart the DTS task.

Sample error message:

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 destination database schema (such as column types or lengths) is inconsistent with the source, preventing data from being written.

Solution: Check the error message and the source database schema, then modify the destination database schema to be consistent with (or compatible with) the source. Restart the DTS task.

Sample error message:

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

Possible cause: Fields in the destination database have data formats that do not meet the requirements, causing function execution to fail.

Solution: Check the error message and the source database schema, then modify the destination database schema to be consistent with (or compatible with) the source. Restart the DTS task.

Sample 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 destination database schema (such as column types or lengths) is inconsistent with the source, preventing data from being written.

Solution: Check the error message and the source database schema, then modify the destination database schema to be consistent with (or compatible with) the source. Restart the DTS task.

Sample error message:

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: Cannot write STRING type data from the source database to the JSON type field in the destination database.

Solution: Check the error message and the source database schema, then modify the destination database schema to be consistent with (or compatible with) the source. Restart the DTS task.

Sample error message:

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

Possible cause: The destination table uses a non-transactional storage engine, preventing data from being written.

Solution: If your business allows, change the destination table to use a transactional storage engine (such as InnoDB), then restart the DTS task.

Sample error message:

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 SSL secure connections.

Solution: Use one of the following methods:

• Method 1: Enable SSL encryption for the source or destination database.

• Method 2: Configure the source or destination database connection to use a non-encrypted method (select Non-encrypted for Encryption).

Sample error message:

com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: SSL Connection required, but not supported by server.

DTS-RETRY-ERR-0342: Unsupported encoding

Possible cause: The destination database or table uses a character set incompatible with the source, preventing data from being written.

Solution: Change the character set of the destination database or table to one compatible with the source, then restart the DTS task.

Sample error message:

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

Possible cause: The destination database is out of memory.

Solution: Upgrade the destination database specifications to increase memory, then restart the DTS task.

Sample error message:

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: Verify that incremental change logs exist in the source database, the destination database is running normally, the destination database schema is compatible with the source, and the destination database account has the required permissions. Then restart the DTS task.

Sample error message:

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 destination database account used by the DTS task cannot write data to the destination database.

Solution: Verify that the destination database account has sufficient write permissions and that the database instance does not restrict writes for that account. Then restart the DTS task.

Sample error message:

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 source or destination database cannot be connected due to insufficient memory.

Solution: Upgrade the source or destination database specifications to increase memory, then restart the DTS task.

Sample error message:

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

Possible cause: DTS timed out when executing a query in the source database.

Solution: Increase the SQL query timeout setting in the source database or upgrade the database specifications, then restart the DTS task.

Sample error message:

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 source or destination database cannot be connected due to insufficient memory.

Solution: Upgrade the source or destination database specifications to increase memory, then restart the DTS task.

Sample 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

Possible cause: The destination database is in read-only or locked state, preventing data from being written.

Solution: Contact the database administrator (DBA) to restore the database, then restart the DTS task.

Sample error message:

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 (.*)?

Possible cause: The connection between the source database and DTS is abnormal due to factors such as network instability.

Solution: Wait 5 minutes, then restart the DTS task. If the issue persists, join the DTS customer communication DingTalk group (group ID: 116655009709) through DingTalk (DingTalk client download link) for consultation.

Sample error message:

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: Null values are being written to columns with NOT NULL constraints in the destination database.

Solution: Check the error message and the source database schema, then modify the destination database schema accordingly (for example, remove the NOT NULL constraint from the problematic column). Restart the DTS task.

Sample error message:

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 life time is shorter than transaction duration

Possible cause: DTS fails to read data due to a timeout caused by the garbage collection (GC) mechanism of the source database.

Solution: Increase the GC timeout period in the source database, then restart the DTS task.

Sample error message:

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: No results were returned when DTS queried data in the source database.

Solution: Check the database status and network connectivity to verify that DTS can connect to the database normally, then restart the DTS task.

Sample error message:

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

Possible cause: DTS cannot connect to the database normally.

Solution: Check the database status, network connectivity, firewall (or security settings), and driver settings to verify that DTS can connect to the database normally. Then restart the DTS task.

Sample 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 database configured for the DTS task is not the primary node, preventing data from being written.

Solution: Reconfigure the DTS task, using the primary node of the database as the destination.

Sample error message:

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

Possible cause: Databases with names that differ only in case exist in the destination, causing data write conflicts.

Solution: If your business allows, clean up the destination instance, then restart the DTS task.

For sync instances, use the Modify Synchronization Objects feature to move the objects causing errors from Selected Objects to Source Objects and submit this change. Then use Modify Synchronization Objects to add them back to Selected Objects, using the Database, Table, and Column Name Mapping feature to write data to other databases in the destination.

Sample error message:

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: The character sets of the tables in the source and destination databases are incompatible, preventing data from being written.

Solution: Use the ErrorUrl in the error message to troubleshoot and resolve the issue, then restart the DTS task. If the issue cannot be resolved, use DingTalk (DingTalk communication client download link) to join the DTS customer communication DingTalk group (Group ID: 116655009709) for consultation.

Sample error message:

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: **** status is fail. Load result: ****

DTS-RETRY-ERR-0360: Operation exceeded time limit

Possible cause: DTS timed out when executing query or write operations.

Solution: Check the status of your MongoDB database instance (such as payload and slow queries), verify that DTS can execute queries and write operations normally, then restart the DTS task.

Sample error message:

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

Possible cause: The destination database is missing tables that exist in the source, preventing data from being written.

Solution: Manually create the missing tables in the destination database, then restart the DTS task.

Sample error message:

DTS-31007: Failed to obtain table **** detail information after retrying. Cause: FatalAnyAllException: common: DTS-100047: Retried 4312 times, 43209 seconds, which exceeds the supposed 43200 seconds RecoverableAnyAllException: replicate-selectdb: DTS-70002: Failed to obtain table **** detail information. SQLException: errCode = 2, detailMessage = Unknown table ****

DTS-RETRY-ERR-0362: Not support string len over than string_type_length_soft_limit_bytes

Possible cause: The length of STRING type data to be written to the destination SelectDB database exceeds the configured limit.

Solution: Increase the string_type_length_soft_limit_bytes parameter of the SelectDB database to accommodate the maximum STRING length being written, then restart the DTS task.

Sample error message:

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

Possible cause: The destination database schema (such as column types or lengths) is inconsistent with the source, preventing data from being written.

Solution: Change the type of the corresponding field in the target index to Object, then restart the DTS task.

Sample error message:

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 target Elasticsearch database does not have the required index.

Solution: Add the missing indexes to the target Elasticsearch database, then restart the DTS task.

Sample error message:

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 target Elasticsearch database is in read-only mode, preventing data from being written.

Solution: Change the target Elasticsearch database to read-write mode, then restart the DTS task.

Sample error message:

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 of the destination Elasticsearch database used by the DTS task is incorrect.

Solution:

• Wrong password: Go to the Basic Information page in the DTS instance console. In the Destination area, click Change Password, enter the correct password for the destination Elasticsearch database, then restart the DTS task.

• Wrong account: Reconfigure the DTS task with the correct database account and password.

Sample error message:

unable to authenticate user [elastic]

DTS-RETRY-ERR-0367: In encoding "UTF8" has no equivalent in encoding "GBK" (.*)?

Possible cause: The destination database or table uses a character set incompatible with the source, preventing data from being written.

Solution: Change the character set of the destination database table (for example, change it to GB18030), then restart the DTS task.

Sample error message:

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 initialization failed.

Solution: Restart the DTS task during off-peak hours, when the CPU load of both the source and destination databases is below 30%.

Sample error message:

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) segment of the source database has been removed.

Solution: Contact the database administrator (DBA) of the source database to resolve the issue, then restart the DTS task.

Sample error message:

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 database account and password configured for the DTS task cannot connect to the database.

Solution:

• Wrong password: Go to the Basic Information page in the DTS instance console. In the Destination area, click Change Password, enter the correct password, then restart the DTS task.

• Wrong account: Reconfigure the DTS task with the correct database account and password.

Sample error message:

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 (.*)?

Possible cause: The database account configured for the DTS task has insufficient permissions. Owner permission is required.

Solution: Grant the required permissions to the database account used by the DTS task, then restart the DTS task. Alternatively, reconfigure the DTS task with a database account that has sufficient permissions.

Sample error message:

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 (.*)?

Possible cause: The database instance cannot be connected.

Solution: Verify that the database can be connected normally, then restart the DTS task.

Sample error message:

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.

Possible cause: The source or destination database is PolarDB for PostgreSQL Distributed Edition.

Solution: None. DTS does not support PolarDB for PostgreSQL distributed clusters.

Sample error message:

DTS-100047: retry 4306 times, 43201 seconds, which exceed the supposed 43200 seconds cause: CriticalAnyAllException: framework: DTS-30011: currentRunningSQL: **** insert ignore into ****,currentRow:null, reason: Incorrect SET value: 'unknown' for column 'permissions' at row 1 BatchUpdateException: Incorrect SET value: 'unknown' for column 'permissions' at row 1 MysqlDataTruncation: Incorrect SET value: 'unknown' for column 'permissions' at row 1

DTS-RETRY-ERR-0374: PostgreSQL logical log not found (.*)?

Possible cause: DTS cannot find the data at the corresponding offset in the source database.

Solution: Check the error message and the source database schema, then modify the destination database schema to be consistent with (or compatible with) the source. Restart the DTS task.

Sample error message:

DTS-100047: retry 4306 times, 43201 seconds, which exceed the supposed 43200 seconds cause: CriticalAnyAllException: framework: DTS-30011: currentRunningSQL: **** insert ignore into ****,currentRow:null, reason: Incorrect BINARY value for column 'hash' at row 1 BatchUpdateException: Incorrect BINARY value for column 'hash' at row 1 MysqlDataTruncation: Incorrect BINARY value for column 'hash' at row 1

DTS-RETRY-ERR-0375: FATAL: terminating connection due to out of memory (.*)?

Possible cause: Database memory OOM (Out of Memory).

Solution: Contact the database administrator (DBA) to resolve the issue, then restart the DTS task.

Sample error message:

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 ETL data processing statement is incorrect, causing ETL execution to fail.

Solution:

• Sync instance: Check and correct the data processing statement, then restart the DTS task.

• Migration instance: Reconfigure the migration task with the correct data processing statement.

Sample error message:

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 (.*)?

Possible cause: Data cannot be written because the network communication between DTS and the destination database timed out.

Solution:

1. Verify that the network connections to the source and destination databases have recovered, and that both databases are running normally and can be connected.

2. In the DTS console, click Restart to restart the DTS task. I/O errors cannot be skipped by using an "ignore" operation. The DTS console provides only the Restart operation, not an "ignore" option.

3. DTS has a built-in automatic retry mechanism. If the source or destination database cannot be connected, DTS retries for up to 720 minutes by default. If the network connection recovers during this period, the task resumes automatically without manual intervention.

4. After you restart the task, it resumes from the point where it was interrupted. Schema migration and full data synchronization are not performed again.

5. This error is caused by abnormal network communication and does not affect data consistency.

Sample error message:

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 initialization failed.

Solution: Restart the DTS task during off-peak hours, when the CPU load of both the source and destination databases is below 30%.

Sample error message:

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 destination database schema (such as column types or lengths) is inconsistent with the source, preventing data from being written.

Solution: Check the error message and the source database schema, then modify the destination database schema to be consistent with (or compatible with) the source. Restart the DTS task.

Sample error message:

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 initialization failed.

Solution: Restart the DTS task during off-peak hours, when the CPU load of both the source and destination databases is below 30%.

Sample error message:

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 data to be synchronized or migrated contains foreign keys, and the destination database account has insufficient permissions (a privileged or superuser account is required).

Solution: Set the session_replication_role parameter in the destination database to replica, then restart the DTS task. After the DTS task is completed or released, reset session_replication_role to origin.

If this parameter is not configured, data inconsistency may occur in special scenarios (such as when cascade updates, cascade deletes, or triggers exist in the destination database).

Sample error message:

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 destination database schema (such as column types or lengths) is inconsistent with the source, preventing data from being written.

Solution: Check the error message and the source database schema, then modify the destination database schema to be consistent with (or compatible with) the source. Restart the DTS task.

Sample error message:

DTS-100047: retry 4306 times, 43201 seconds, which exceed the supposed 43200 seconds cause: CriticalAnyAllException: framework: DTS-30011: currentRunningSQL: **** insert ignore into ****,currentRow:null, reason: Incorrect MULTILINESTRING value for column 'routes' at row 1 BatchUpdateException: Incorrect MULTILINESTRING value for column 'routes' at row 1 MysqlDataTruncation: Incorrect MULTILINESTRING value for column 'routes' at row 1

DTS-RETRY-ERR-0384: Function "TIMESTAMP" not found (.*)?

Possible cause: The filter condition configured in the DTS task contains objects that do not exist in the source database.

Solution:

• Sync task: Use the modify synchronization object feature to update the Filter Conditions. For more information, see What to do next.

• Migration task: Reconfigure the migration task with the correct filter condition.

Sample error message:

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: The destination database configured for the DTS task is not the primary node, preventing data from being written.

Solution: Contact the database administrator (DBA) to resolve the issue, then restart the DTS task.

Sample error message:

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: The table name in the source or destination database contains special characters.

Solution: Please use DingTalk (DingTalk client download link) to join the DTS customer communication DingTalk group (group number: 116655009709) for consultation.

Sample error message:

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: You disconnected the connection between DTS and the database.

Solution: Check the error message and the source database schema, then modify the destination database schema to be consistent with (or compatible with) the source. Restart the DTS task.

Sample error message:

DTS-100047: retry 4306 times, 43201 seconds, which exceed the supposed 43200 seconds cause: CriticalAnyAllException: framework: DTS-30011: currentRunningSQL: **** insert ignore into ****,currentRow:null, reason: Incorrect INET value for column 'ip_address' at row 1 BatchUpdateException: Incorrect INET value for column 'ip_address' at row 1 MysqlDataTruncation: Incorrect INET value for column 'ip_address' at row 1

DTS-RETRY-ERR-0388: Index row size (.*)? exceeds btree version (.*)? maximum (.*)? for index

Possible cause: The destination database schema (such as column types or lengths) is inconsistent with the source, preventing data from being written.

Solution: Check the error message and the source database schema, then modify the destination database schema to be consistent with (or compatible with) the source. Restart the DTS task.

Sample error message:

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.

DTS-RETRY-ERR-0390: Invalid column index

Possible cause: The data to be synchronized or migrated from the source database contains invalid indexes.

Solution:

• Sync task: Use the Modify Objects feature to remove objects with invalid indexes from the sync scope, then restart the DTS task.

• Migration task: Reconfigure the DTS task and exclude objects with invalid indexes from the migration scope.

Sample error message:

DTS-52111: Increment Context Is Not Running..: cause: CriticalAnyAllException: oracle-reader: DTS-52340: Serializer redo log entry failed CriticalAnyAllException: oracle-reader: DTS--0001: execute sql select *** from *** where *** in (?) 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 CriticalAnyAllException: oracle-reader: DTS-52340: Invalid column index SQLException: Invalid column index

DTS-RETRY-ERR-0391: Unable to open backup device

Possible cause: The logs of the source database have been cleared.

Solution:

• Synchronization task: Use the Modify Synchronization Objects feature to remove objects containing invalid indexes from the synchronization objects, then restart the DTS task.

• Migration task: Reconfigure the DTS task, and do not select objects containing invalid indexes as the objects to be migrated.

Sample error message:

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: sqlserver-reader: DTS-52410: Sqlserver log fetch failed IOException: com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open backup device 'D:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Backup\VNBU0-***-***-***'. Operating system error 2(The system cannot find the file specified).

DTS-RETRY-ERR-0392: InvalidWireTypeException: Protocol message tag had invalid wire type

Possible cause: The Kafka Data Source Component of the TiDB database is incorrectly configured.

Solution: Reconfigure the DTS task and select the correct Kafka Data Source Component for your situation.

Sample error message:

DTS-31009: In process of processing data (recordRange: 8118513945741****) failed cause: FatalAnyAllException: common: DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 43200 seconds RuntimeException: seek timestamp for topic [****-0] with timestamp [17386372****] failed InvalidWireTypeException: Protocol message tag had invalid wire type.

DTS-RETRY-ERR-0393: Unable to open the requested database(.*) for logon. Logon failed

Possible cause: The source database cannot be connected.

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

Sample error message:

com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open the database "db01" requested by the logon. Logon failed. ClientConnectionId:9d0c3b2f-923a-46cd-****

DTS-RETRY-ERR-0394: User (.*) logon failed

Sample error message:

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: sqlserver-reader: DTS-52410: Sqlserver log fetch failed IOException: com.microsoft.sqlserver.jdbc.SQLServerException: User *** logon failed. ClientConnectionId:bec357eb-88ea-4fa6-a475-dcc07a**** SQLServerException: User *** logon failed.

DTS-RETRY-ERR-0395: User (.*) does not have permission to run DBCC TRACEON

Possible cause: The database account has insufficient permissions.

Solution:

• Method 1: Grant sufficient permissions to the database account used in the DTS task, and then restart the DTS task.

• Method 2: Configure the DTS task using a database account with sufficient permissions.

Sample error message:

DTS-52110: SQLServerRecordExtractor Init Error: sqlserver-reader: DTS-00032: execute sql DBCC TRACEON(2537,-1) failed, case by common: DTS-100047: retry 0 times, 0 seconds, which exceed the supposed 43200 seconds cause: CriticalAnyAllException: sqlserver-reader: DTS-00032: execute sql DBCC TRACEON(2537,-1) 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 SQLServerException: User *** does not have permission to run DBCC TRACEON.

DTS-RETRY-ERR-0397: An I/O error occurred while sending to the backend. SocketTimeoutException: Read timed out

Possible cause: Network communication timeout between DTS and the database.

Solution: Verify that the database is running normally and DTS can connect to it, then restart the DTS task.

Sample error message:

DTS-100047: retry 11 times, 43315 seconds, which exceed the supposed 43200 seconds cause: CriticalAnyAllException: framework: DTS-30011: currentRunningSQL: /* DTS-full-kv7n180xb34815h */insert into ****** 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-0398: Cannot get offset for timestamp

Sample error message:

DTS-073102: Record Crawler error. cause by [Cannot get offset for timestamp: 1733994****] About more information in ****

DTS-RETRY-ERR-0399: Cannot open backup device

Possible cause: The logs of the source database have been cleared.

Solution: Use one of the following methods:

• Method 1: Contact the database administrator (DBA) of the source database to resolve the issue, then restart the DTS task.

• Method 2: Reconfigure the DTS task.

Sample error message:

DTS-100047: retry 0 times, 20124 seconds, which exceed the supposed 43200 seconds cause: CriticalAnyAllException: dts-k-src: DTS-52111: Increment Context Is Not Running..: CriticalAnyAllException: sqlserver-reader: DTS-52410: Sqlserver log fetch failed IOException: com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open backup device **** Operating system error 2(The system cannot find the file specified).

DTS-RETRY-ERR-0400: Cannot open database (.*)? requested by the login. The login failed

Sample error message:

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: sqlserver-reader: DTS-52410: Sqlserver log fetch failed IOException: com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open database "****" requested by the login. The login failed. ClientConnectionId:778b469a-d689-4**** SQLServerException: Cannot open database "****" requested by the login. The login failed.