Failed to Create Task in DM Web

Translated
1

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

Original topic: DM Web创建任务失败

| username: TiDBer_hwEZA4rV

When configuring the task, the following error occurred, and I couldn’t understand what the error was:

code=26005:class=dm-master:scope=internal:level=medium], Message: fail to check synchronization configuration with type: check was failed, please see detail detail: { “results”: [ { “id”: 10, “name”: “sharding table tidb_simulation.* consistency checking”, “desc”: “check consistency of sharding table structures”, “state”: “fail”, “errors”: [ { “severity”: “fail”, “short_error”: “sourceID 10_21_82_28 table simulation.data_exchange_task of sharding tidb_simulation.* have auto-increment key, please make sure them don’t conflict in target table!” }, { “severity”: “fail”, “short_error”: “sourceID 10_21_82_28 table simulation.progress of sharding tidb_simulation.* have auto-increment key, please make sure them don’t conflict in target table!” }, { “severity”: “fail”, “short_error”: “column length mismatch (self: 13 vs other: 7)”, “self”: “sourceID 10_21_82_28 table simulation.data_exchange_task columns [id gmt_create gmt_modify simulation_uuid fetch_data_task_id status job_key out_status attribute request attribute_version finish_time task_type]”, “other”: “sourceID 10_21_82_28 table simulation.progress columns [id task_uuid total current_value gmt_create gmt_modify biz_type]” }, { “severity”: “fail”, “short_error”: “sourceID 10_21_82_28 table simulation.sample of sharding tidb_simulation.* have auto-increment key, please make sure them don’t conflict in target table!” }, { “severity”: “fail”, “short_error”: “column length mismatch (self: 13 vs other: 33)”, “self”: “sourceID 10_21_82_28 table simulation.data_exchange_task columns [id gmt_create gmt_modify simulation_uuid fetch_data_task_id status job_key out_status attribute request attribute_version finish_time task_type]”, “other”: “sourceID 10_21_82_28 table simulation.sample columns [id uuid name partner_code app_name app_type event_type status reason total white_total black_total default_total create_by history gmt_create gmt_modify gmt_success description history_draw statistic gmt_start gmt_end partner_display_name app_display_name event_display_name params attribute attribute_version source test_id encryption encryption_param]” }, { “severity”: “fail”, “short_error”: “sourceID 10_21_82_28 table simulation.sample_data of sharding tidb_simulation.* have auto-increment key, please make sure them don’t conflict in target table!” }, { “severity”: “fail”, “short_error”: “column length mismatch (self: 13 vs other: 12)”, “self”: “sourceID 10_21_82_28 table simulation.data_exchange_task columns [id gmt_create gmt_modify simulation_uuid fetch_data_task_id status job_key out_status attribute request attribute_version finish_time task_type]”, “other”: “sourceID 10_21_82_28 table simulation.sample_data columns [id uuid sample_uuid seq_id data_type event_occur_time event_data final_score final_decision gmt_create gmt_modify custom_matching_id]” }, { “severity”: “fail”, “short_error”: “sourceID 10_21_82_28 table simulation.dc_account of sharding tidb_simulation.* have auto-increment key, please make sure them don’t conflict in target table!” }, { “severity”: “fail”, “short_error”: “column length mismatch (self: 13 vs other: 8)”, “self”: “sourceID 10_21_82_28 table simulation.data_exchange_task columns [id gmt_create gmt_modify simulation_uuid fetch_data_task_id status job_key out_status attribute request attribute_version finish_time task_type]”, “other”: “sourceID 10_21_82_28 table simulation.dc_account columns [id gmt_create gmt_modify account app_key app_secret status priority]” }, { “severity”: “fail”, “short_error”: “sourceID 10_21_82_28 table simulation.simulation of sharding tidb_simulation.* have auto-increment key, please make sure them don’t conflict in target table!” } ], “instruction”: “please set same table structure for sharding tables”, “extra”: “error on sharding tidb_simulation.*” } ], “summary”: { “passed”: false, “total”: 11, “successful”: 10, “failed”: 1, “warning”: 0 } }

2
| username: xfworld | Original post link

“The log describes it, check according to this: sourceID 10_21_82_28 table simulation.data_exchange_task of sharding tidb_simulation.* have auto-increment key, please make sure they don’t conflict in the target table!”

3
| username: TiDBer_hwEZA4rV | Original post link

The target TiDB is an empty database, what conflicts are being checked…

4
| username: wuxiangdong | Original post link

The number of columns in the source table and the target table is different.

5
| username: wuxiangdong | Original post link

First, try configuring a specific table, replacing the asterisk with the actual table name.

6
| username: TiDBer_hwEZA4rV | Original post link

There is no problem with assigning only one table, but is there an issue with the regular expression?

7
| username: TiDBer_hwEZA4rV | Original post link

It seems that the target table cannot use *

8
| username: wuxiangdong | Original post link

The downstream might not need to be filled in at all.

9
| username: buchuitoudegou | Original post link

The error of column count mismatch is likely caused by the synchronization rule configuration. The “table” configuration item downstream should not be filled. If it is filled, it might be considered as a merge of databases and tables migration, thus it needs to determine whether the column counts of the tables matching this rule are the same.

The same goes for the auto-increment key error.