DM Non-DDL Statement Synchronization Error

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: dm非DDL语句同步报错

| username: tuyi锅子

【TiDB Usage Environment】Testing Environment
【TiDB Version】6.1
【Encountered Issue】
DM synchronization error, query-status shows that there is a table creation statement in the binlog, and the synchronization is interrupted because the comment of one of the fields is too long.
After using binlog skip, it reports “msg”: “only support to handle ddl error currently”.
I would like to ask if DM can skip non-DDL operations.

2
| username: songxuecheng | Original post link

Creating a table with field descriptions that are too long causes an interruption? Isn’t it just a DDL?

3
| username: tuyi锅子 | Original post link

The description was incorrect; it was an insert statement error. After modifying the comment of the error field, the synchronization worked fine.

4
| username: songxuecheng | Original post link

This is also incorrect. If you want to modify the comments, it should be a DDL statement. You can directly refer to skipping DDL.

5
| username: tuyi锅子 | Original post link

The error is with the insert statement, which is being synchronized from MySQL to TiDB. The comment was modified directly on TiDB.

6
| username: songxuecheng | Original post link

Please send the query-status.

7
| username: wakaka | Original post link

Comments? Or values?

8
| username: Hacker007 | Original post link

Non-DDL issues need to be resolved manually, such as primary key conflicts.

9
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. No new replies are allowed.