TICDC Synchronization Failure Due to DDL Statement Not Specifying Database

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

Original topic: TICDC因DDL语句未指定database导致同步失败

| username: TiDBer_Bj7TDCTL

[TiDB Usage Environment] Testing
[TiDB Version] 7.1.1
[Reproduction Path]
There are currently 2 TiDB clusters A and B.
ticdc has been set up, data flows from A to B.
The test environment has 2 test databases t1 and t2.
Create a test table in t2 of cluster A:

CREATE TABLE t2.origin_table (
id int,
name text,
PRIMARY KEY (id)
);

At this point, the table creation operation is normally applied in cluster B.

Then enter database t2 in cluster A:

use t2;

Execute:

CREATE TABLE t1.origin_table_1 like origin_table;

The table in t1 is successfully created in cluster A.
ticdc directly reports an error: “[CDC:ErrChangefeedUnretryable] changefeed is in unretryable state, please check the error message, and you should manually handle it: Error 1146 (42S02): Table ‘t1.origin_table’ doesn’t exist”

[Encountered Problem: Problem Phenomenon and Impact]
ticdc synchronization error

[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots/Logs/Monitoring]

| username: xfworld | Original post link

Isn’t this a normal error?

| username: 小龙虾爱大龙虾 | Original post link

This is normal behavior. CDC will switch to the schema of the DDL to execute the DDL. You can skip this DDL, or temporarily create the origin_table in the downstream t1 database to allow the DDL to execute normally.

| username: wangccsy | Original post link

Try looking at the help manual.

| username: oceanzhang | Original post link

After looking at it for a long time, it turns out to be a “dei”.

| username: 随缘天空 | Original post link

Check the database permissions issue before synchronization.

| username: dba远航 | Original post link

Normal behavior