Issues with the dm_meta Database

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

Original topic: dm_meta库问题

| username: h5n1

meta-schema: “dm_meta” # The database for storing meta information downstream
When DM starts the task, it will create a synchronization metadata database downstream, but the downstream DRDS does not support this syntax.
fail to initialize checker: execute statement failed: CREATE SCHEMA IF NOT EXISTS dm_meta, RawCause: Error 1064 (HY000)
Is there any way to prevent DM from executing this statement or to store the meta information in a file?

| username: guominghao | Original post link

None :slightly_frowning_face: :slightly_frowning_face:

| username: h5n1 | Original post link

Can such a requirement be raised?

| username: guominghao | Original post link

The downstream is not TiDB, so PM probably won’t support it.

| username: h5n1 | Original post link

I think the official team should develop ecosystem tools like Dumpling and DM to support multiple databases, which might increase the usage rate of TiDB. The current requirement I am facing is to write data from upstream MySQL sharding to downstream Alibaba DRDS. Sometimes, we need to export data from DRDS. We haven’t used TiDB in production yet, but using such tools might create some opportunities.

| username: 考试没答案 | Original post link

Can you create it manually???

| username: 考试没答案 | Original post link

Your alternative solution: manually synchronize the full data, then perform incremental transmission.

| username: 考试没答案 | Original post link

If the downstream database is DRDS, the table structure must have undergone sharding. You only need the data, right?