DM Synchronization Error

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

Original topic: DM同步报错

| username: terry0219

[TiDB Usage Environment] Production Environment / Testing / Poc
[TiDB Version] 7.5.1
Error Message:
“errors”: [
{
“ErrCode”: 44006,
“ErrClass”: “schema-tracker”,
“ErrScope”: “internal”,
“ErrLevel”: “high”,
“Message”: “startLocation: [position: (mysql-bin.010356, 40326), gtid-set: 42711b39-f09a-11ed-9cf6-fa163ecd3002:1-8350205,777bcc38-d41f-11ed-bbe9-fa163ecd6496:1-382776,f342f0d2-ee25-11ed-a969-fa163ecd511c:1-165967], endLocation: [position: (mysql-bin.010356, 40547), gtid-set: 42711b39-f09a-11ed-9cf6-fa163ecd3002:1-8350206,777bcc38-d41f-11ed-bbe9-fa163ecd6496:1-382776,f342f0d2-ee25-11ed-a969-fa163ecd511c:1-165967], origin SQL: [ALTER TABLE xxx\r\n\tCHANGE COLUMN id id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT COMMENT ‘ID’ FIRST]: cannot track DDL: ALTER TABLE xxx.xxx CHANGE COLUMN id id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT COMMENT ‘ID’ FIRST”,
“RawCause”: “[ddl:8200]Unsupported modify column: can’t set auto_increment”,
“Workaround”: “You can use handle-error to replace or skip this DDL.”
}
],

The prompt “Unsupported modify column: can’t set auto_increment” appears. How can this be resolved?

| username: hey-hoho | Original post link

Refer to this operation to skip DDL

| username: 啦啦啦啦啦 | Original post link

It is not supported to use ALTER TABLE to add the AUTO_INCREMENT attribute, including using the ALTER TABLE ... MODIFY/CHANGE COLUMN syntax to add the AUTO_INCREMENT attribute to an existing column, and using the ALTER TABLE ... ADD COLUMN to add a column with the AUTO_INCREMENT attribute.
Refer here:

Follow the method suggested by the expert above to bypass this.