为提高效率,提问时请提供以下信息,问题描述清晰可优先响应。
- 【TiDB 版本】:tidb 4.0.9
- 【问题描述】:DM 2.0.1 数据同步故障
“ErrCode”: 44007,
“ErrClass”: “schema-tracker”,
“ErrScope”: “downstream”,
“ErrLevel”: “medium”,
“Message”: “startLocation: [position: (3301-binlog.000004, 1224291), gtid-set: ], endLocation: [position: (3301-binlog.000004, 1224875), gtid-set: ]: cannot fetch downstream table schema ofh3_job
.xxl_job_qrtz_triggers
to initialize upstream schemah3_job
.xxl_job_qrtz_triggers
in schema tracker”,
“RawCause”: “Error 1146: Table ‘h3_job.xxl_job_qrtz_triggers’ doesn’t exist”,
“Workaround”: “”
同样的表在tidb 3.0.12+dm 1.0.4上同步正常的。
该表xxl_job_qrtz_triggers是有外键, 这个问题改怎么处理,同步到TIDB可以不使用外键。 怎么跳过外键??
Create Table: CREATE TABLE xxl_job_qrtz_triggers
(
SCHED_NAME
varchar(120) NOT NULL,
TRIGGER_NAME
varchar(200) NOT NULL,
TRIGGER_GROUP
varchar(200) NOT NULL,
JOB_NAME
varchar(200) NOT NULL,
JOB_GROUP
varchar(200) NOT NULL,
DESCRIPTION
varchar(250) DEFAULT NULL,
NEXT_FIRE_TIME
bigint(13) DEFAULT NULL,
PREV_FIRE_TIME
bigint(13) DEFAULT NULL,
PRIORITY
int(11) DEFAULT NULL,
TRIGGER_STATE
varchar(16) NOT NULL,
TRIGGER_TYPE
varchar(8) NOT NULL,
START_TIME
bigint(13) NOT NULL,
END_TIME
bigint(13) DEFAULT NULL,
CALENDAR_NAME
varchar(200) DEFAULT NULL,
MISFIRE_INSTR
smallint(2) DEFAULT NULL,
JOB_DATA
blob,
PRIMARY KEY (SCHED_NAME
,TRIGGER_NAME
,TRIGGER_GROUP
) USING BTREE,
KEY SCHED_NAME
(SCHED_NAME
,JOB_NAME
,JOB_GROUP
) USING BTREE,
CONSTRAINT XXL_JOB_QRTZ_TRIGGERS_ibfk_1
FOREIGN KEY (SCHED_NAME
, JOB_NAME
, JOB_GROUP
) REFERENCES xxl_job_qrtz_job_details
(SCHED_NAME
, JOB_NAME
, JOB_GROUP
)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 ROW_FORMAT=DYNAMIC
还有一个表结构没什么异常,同步也报错表不存在
"Message": "startLocation: [position: (3303-binlog.000002, 2223), gtid-set: ], endLocation: [position: (3303-binlog.000002, 2866), gtid-set: ]: cannot fetch downstream table schema of `activiti`.`act_re_deployment` to initialize upstream schema `activiti`.`act_re_deployment` in schema tracker",
"RawCause": "Error 1146: Table 'activiti.act_re_deployment' doesn't exist",