6G database Import report All kinds of wrong solutions _mysql

Tool Selection
One. SQLyog This tool is still very powerful, but in the face of 5 G database, can only strike, simply, the native import can, from the local import server.
Two. Phpadmin with this pretty people said it is OK, but the last use, the reason is not visible, because up to 50M, although modify the configuration file can upload but 5 g or forget it, not that confidence.
Three. There is also a PHP script. It seems the Germans wrote it. This thing, but also import data, how to say, I did not test success. But the online applause, I was 5G data did not point to success, it is tossing the next day.
Four. Database segmentation Import This I also used, each 100M split, sweat. It can't be any smaller. Split out more than 60 SQL, or will report various errors. The tool also failed. If you want to use it, go online and find it. MySQL Split

The following picture is the successful import of the picture,
The GZ compression type 1.3G decompression becomes 4.52G. Import into the database, it becomes 6.6G ...

Finally, it's in the command.
Mysql-uroot-p shujukuming<xxxxx

Say the wrong word.
Simply put, all kinds of mistakes can be met.
Error 1
ERROR 5 (HY000) at line 318:out of memory (Needed 1681784 bytes)

This error can be reported by a lot of use-F, the general meaning is not enough memory,
Solution: Mysql-uroot-p shujukuming-f<xxxxx
If you don't mind losing a few data, use the above method.

Error 2
ERROR 1062 (23000) at line 30:duplicate entry ' 1 ' for key ' PRIMARY '
This error is the meaning of the key value error
Solution: The net is to empty the data table data, but in the data partition when the primary key and partition can not be used at the same time, the primary key changes on the line

Error 3
MySQL error nr.2006-mysql server has gone away
This error is a problem with uploading restrictions and needs to modify the configuration file
Config file in Linx called my.conf in Windows called My.ini
The things in this change to be careful of the change is not possible.
The simple thing to do is to modify a few configurations.

max_allowed_packet=166666m this is to limit the size of the file due to upload 6 g so it should be enough to 1111111M.
wait_timeout=288000000 wait for timeout. See things change, I added several 0 in the back ...
interactive_timeout= 288000000 Run timeout .... See things change, I added several 0 in the back ...

Do not modify other configuration files except for a few, and be aware of restarting the server

Error 4
This is a very low-level mistake.
MySQL version not right now, it's all 5.0+.
Note that the high version cannot import the low version, 5.5+ is not supported by some query statements that cannot be imported into 5.0+.

Reprint Please indicate the source thank you http://skss.blog.163.com/

The above is I encountered a variety of problems, if there are other questions please advise, after all, 6 g of the file what SQL also can not open