Solve the problem of garbled data in MySQL database migration

Under the instructions of my leader, I took over a Java project and needed to refactor it. At the same time, the overall construction of the project had to meet the requirements of information innovation.
Then first of all, two points must be met:
1. Use the domestic database Dameng 8 to replace the MySQL database
2. Use Kingdee middleware to replace tomcat for container deployment

With unremitting efforts, I have completed the local construction and installation of the DM8 database, and also completed the demo verification work of changing the database source in the code framework and replacing the DM8 database.

driverClassName: dm.jdbc.driver.DmDriver
    url: jdbc:dm://10.0.3.132:5236/XC-SERVICE?zeroDateTimeBehavior=convertToNull&useUnicode=true&characterEncoding=utf-8
    Username: XC-SERVICE
    password: 123456789

Now the code works fine. There are no other problems except that some SQL scripts need to be standardized.

Now the most important thing is to migrate the data.

That is to migrate the mysql library to dm8.
Migration method: use DAMO's own database migration tool

DAMO comes with a database migration tool

Data table structure and data migration effects

After the migration is complete, you will be surprised to find that there is no problem with the data table structure, but the Chinese data is all garbled.

I tried many methods and searched on Baidu several times, but couldn't find a solution. Later, I had no choice but to go to the DAMO forum to look for a solution.

Finally, I found a magical solution to the problem of garbled characters after data migration.

When using the data migration tool to configure the data source, select Specify Driver.

Specify the URL address:

jdbc:mysql://10.0.3.131:3306/sys-service?useUnicode=true&characterEncoding=UTF-8&useSSL=false&serverTimezone=Asia/Shanghai

At the same time, specify the driver that Maven downloads to the local computer.

OK, now we can migrate the data

After the migration is complete, you will magically find that the data is normal and not garbled! ! ! !

postscript

As for the domestically produced database, DAMO is still a good product, but there is too little information on the Internet, and you may not be able to find it on Baidu. I write this content in the hope that it will be helpful to you.

This is the end of this article about solving the problem of garbled data in MySQL database data migration. For more relevant content about garbled data in MySQL migration, please search for previous articles on 123WORDPRESS.COM or continue to browse the related articles below. I hope you will support 123WORDPRESS.COM in the future!