Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: 使用dm进行全量导入，但是没有看到数据
|
username: 烂番薯0
Dear experts, I am using DM for full data import, but I don’t see any data in the database. What could be the reason for this?
Data source
Task
This is the status
However, no data is being imported, and the speed is very slow. How can I improve this?
Currently, this number of rows is very slow, increasing one by one.
Use “*” directly for the tbl-name parameter, do not add the database name.
I remember there was a database naming convention, check the official documentation.
Buddy, I followed your instructions and made the changes, but it resulted in an error.
This error indicates that the table does not exist in your downstream.
However, I am using the full import mode. Shouldn’t the downstream table be imported from the upstream by DM?
There is no problem with the table names and such because I don’t need to sync all the tables. I listed them one by one.
The documentation contains examples, and it is written very clearly here. I suggest reading it carefully three times before asking questions: docs-cn/dm/task-configuration-file-full.md at release-6.5 · pingcap/docs-cn · GitHub
I suggest you stop the task, clear the downstream, and then re-import, especially dm_meta. The configuration file doesn’t seem to have any issues. By the way, please provide the TiDB and DM versions.
I suspect this error is due to DM switching to incremental import. Since you previously stopped the task, modified the configuration file, and restarted it, but didn’t clean up the downstream properly, it resulted in skipping table creation and directly executing data import operations. The documentation also mentions that restarting a task requires cleaning up the downstream. When restarting the task, add the --remove-meta configuration.
Data Migration FAQ | PingCAP Documentation Center
Hmm… The version is V6.5.0. After I started the downstream database task, no data was generated. Then, I followed the official procedure to modify the file and restarted the cluster, but it reported the above error, saying that there is no table in the downstream…
I understand, it’s normal for the downstream to have no data when the task is just created. This is because the synchronization logic of DM is to pull the upstream data into the dm-worker at the moment you start the task, then fully import it into the downstream, and then execute incremental synchronization. When you start the task, you can observe that your dm-worker will have an additional directory, which stores the SQL files of the upstream table structure and data.
|
username: 
|
username: 
|
username: 
|
username: