The garbled problem of MySQL

MySQL's garbled files
This afternoon, the relocation server; the transfer data was killed. Since the data was upgraded to a newer version of MySQL, all the problems in the relocation process occurred.

Because the default character set used when starting a database is gb2312 a bit of a problem with MySQL after the upgrade, and finally the setchar=gb2312 of the data is removed;

Then SetChar's text set depends on your MySQL my.cnf when the default character set file is used; If the default is gb2312 there is no way you will setchar remove the characters you come out or gb2312

So you can change the setchar=gb2312 to setchar=latin1. The default startup character set of the my.cnf file is removed from the new boot MySQL.