DM 44007 Error

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

Original topic: dm 44007错误

| username: Jjjjayson_zeng

[TiDB Usage Environment] Production Environment
[TiDB Version] dm v5.4.0
[Reproduction Path] Operations performed that led to the issue
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration]
[Attachment: Screenshot/Log/Monitoring]

As shown in the image, the same error as always.

| username: tidb狂热爱好者 | Original post link

The table does not exist.

| username: Jjjjayson_zeng | Original post link

Why does it not exist? If the upstream deletes it, the downstream should also synchronize it.

| username: xingzhenxiang | Original post link

If it really doesn’t work, manually handle it.

| username: Jjjjayson_zeng | Original post link

This is how it’s done now, but each time it’s only after the fact. Otherwise, you can observe it yourself.

| username: Jjjjayson_zeng | Original post link

Moreover, there are many tasks under a manually affected data source, making it difficult to change.

| username: 小王同学Plus | Original post link

Is your task configuration set to skip the drop statement? Can you provide the complete task configuration for us to check?