Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: tidb dm同步maridb的数据报错
|
username: TI表弟
[TiDB Usage Environment] Test Environment
[TiDB Version]
5.4.0
[Reproduction Path] Sync data from MariaDB 10.2.0 to TiDB
[Encountered Problem: Problem Phenomenon and Impact]
{
“result”: false,
“msg”: “[code=38032:class=dm-master:scope=internal:level=high], Message: some error occurs in dm-worker: ErrCode:36067 ErrClass:"sync-unit" ErrScope:"internal" ErrLevel:"high" Message:"startLocation: [position: (mysql-bin-changelog.2294783, 411), gtid-set: 0-4339686-332669112024], endLocation: [position: (mysql-bin-changelog.2294783, 578), gtid-set: 0-1898801397-332669112025], origin SQL: [SET STATEMENT max_statement_time=60 FOR DELETE FROM mysql.rds_sysinfo where name = ‘innodb_txn_key’]: parse DDL: SET STATEMENT max_statement_time=60 FOR DELETE FROM mysql.rds_sysinfo where name = ‘innodb_txn_key’" RawCause:"line 1 column 32 near \"max_statement_time=60 FOR DELETE FROM mysql.rds_sysinfo where name = ‘innodb_txn_key’\" " Workaround:"Please confirm your DDL statement is correct and needed. For TiDB compatible DDL, see MySQL Compatibility | PingCAP Docs. You can use handle-error command to skip or replace the DDL or add a binlog filter rule to ignore it if the DDL is not needed." , Workaround: Please execute query-status to check status.”,
“source”: “remote_vehicle_prod”,
“worker”: “dm-10.131.188.4-8262”
}
[Resource Configuration]
[Attachment: Screenshot/Log/Monitoring]
Configured filter according to the prompt, but still keeps reporting errors
|
username: 
|
username: