[Test Environment for TiDB] Testing
[TiDB Version] v5.4.3
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Phenomenon and Impact] 111
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]
After deploying the DM 5.4.3 cluster, I migrated from the source MySQL 5.7.34 to the TiDB V5.4.3 cluster. The check passed, so I started the data migration task. The status showed as Finished, and the progress was 100%. However, the source database had 1473 tables, while the target database had 1441 tables, missing 32 tables. How can I troubleshoot this?
During the check phase, there was a type of Warning stating that foreign keys could be parsed but would be ignored by TiDB. After the migration, I found that these tables did exist. There were more than 40 tables without primary keys and unique indexes, which I manually added before the migration. Random checks on a few tables also showed that they were successfully migrated.
You can try again. Additionally, the stored procedures, triggers, and functions in the MySQL source database did not migrate along with the database. How can they be migrated?
None of these are supported. Compare them yourself.
For large MySQL databases, none of what you mentioned would be used. Our entire company does not have a single stored procedure or trigger.
If you use views, let me add one more thing (in case you need to use dumpling for data export later). By default, dumpling does not export views. However, dumpling has parameters that can be modified -W or --no-views set to false to include views.