Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: dm 44007错误
[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.
The table does not exist.
Why does it not exist? If the upstream deletes it, the downstream should also synchronize it.
If it really doesn’t work, manually handle it.
This is how it’s done now, but each time it’s only after the fact. Otherwise, you can observe it yourself.
Moreover, there are many tasks under a manually affected data source, making it difficult to change.
Is your task configuration set to skip the drop statement? Can you provide the complete task configuration for us to check?