Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: 使用DMv6.5.0将 Mysql 8.0.28迁移到TiDBv6.5.0,collation is not same错误
[Test Environment for TiDB] Testing
[TiDB Version] v6.5.0
[Reproduction Path] Using DM v6.5.0 to migrate MySQL 8.0.28 to TiDB v6.5.0
[Encountered Issue: Phenomenon and Impact] The upstream is a business database, and TiDB is used for BI and reporting in the test. An error occurred during table structure migration, and the table structure has been pre-created in TiDB. Starting the DM task resulted in an error, and no data was synchronized.
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]
[tidb@TiTest opt]$ tiup dmctl --master-addr=172.16.86.60:8261 start-task dm-task.yaml
tiup is checking updates for component dmctl …
A new version of dmctl is available:
The latest version: v6.6.0
Local installed version: v6.5.0
Update current component: tiup update dmctl
Update all components: tiup update --all
Starting component dmctl
: /home/tidb/.tiup/components/dmctl/v6.5.0/dmctl/dmctl --master-addr=172.16.86.60:8261 start-task dm-task.yaml
{
“result”: false,
“msg”: “[code=46014:class=scheduler:scope=internal:level=medium], Message: subtasks with name dm-taskX for sources [mysql-replica-sit8641w mysql-replica-uat8721w] already exist, Workaround: Please use query-status
command to see tasks.”,
“sources”: [
],
“checkResult”: "fail to check synchronization configuration with type: no errors but some warnings
…
{
“id”: 22,
“name”: “table structure compatibility check”,
“desc”: “check compatibility of table structure”,
“state”: “warn”,
“errors”: [
{
“severity”: “warn”,
“short_error”: “table master
.mdc_invoice_address
collation is not same, upstream: (mdc_invoice_address utf8mb4_0900_ai_ci), downstream: (mdc_invoice_address utf8mb4_bin)”
}