Syntax Error in DM Load

Translated
1

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

Original topic: dm load语法错误

| username: TiDBer_hwEZA4rV

DM version v6.5.1 encountered an error during the load phase when migrating from mysqlA to mysqlB
“error_msg”: “[code=34019:class=load-unit:scope=not-set:level=high], Message: , RawCause: Error 1064 (42000): 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 ‘config where Type = ‘tidb’ and name = ‘keyspace-name’’ at line 1.\n**”, “load_status”: { “finished_bytes”: 0, “meta_binlog”: “(mysql-bin.001013, 44851597)”, “meta_binlog_gtid”: “033d4f91-d850-11e9-a37f-fa852cf3dd00:1-4613734,2a37f2cd-d850-11e9-aa78-fa338dfa7a00:1-1690484”, “progress”: “0.00 %”, “total_bytes”: 0 }, “name”: “gaea2pudao”, “source_name”: “gaea”, “stage”: “Paused”, “unit”: “Load”, “unresolved_ddl_lock_id”: “”, “worker_name”: “dm-192.168.86.93-8268”

2
| username: tidb菜鸟一只 | Original post link

DM is used to migrate data from MySQL to TiDB. It seems that during the pre-check, your downstream MySQL does not support TiDB’s syntax.

3
| username: Running | Original post link

DM is used to solve the migration problem from MySQL to TiDB. If both the source and target are MySQL, it is recommended to use MySQL ecosystem tools.

4
| username: TiDBer_hwEZA4rV | Original post link

Is it possible to downgrade from v6.5.0 to v6.5.1?

5
| username: Hacker007 | Original post link

Not supported