Mysql – Importing huge dumps into a thesql server 5.5

You could try to use MySQL's CHECK TABLE and REPAIR TABLE functions (but make sure you grab a copy of the table first):

mysql -uroot -p database1
CHECK TABLE table1

If that doesn't work, try using:

CHECK TABLE table1 EXTENDED

According to the CHECK TABLE documentation:

EXTENDED is to be used only after you have run a normal check but still get strange errors from a table when MySQL tries to update a row or find a row by key. This is very unlikely if a normal check has succeeded.

If any errors are reported by either of the above, try:

REPAIR TABLE table1

If that doesn't work, you can try:

REPAIR TABLE table1 EXTENDED

Finally, if that still doesn't work, you may be able to use myisamchk while MySQL is offline - according to the documentation:

REPAIR TABLE does not implement all the options of myisamchk

The plugins throwing errors in the error.log were not specifically specified in my.cnf. So I ran...

select * from mysql.plugin

for MySQL 5.6.17 I deleted the following rows in mysql.plugin

innodb ha_innodb.so
federated ha_federated.so
blackhole ha_blackhole.so
archive ha_archive.so

Do not delete anything you are not sure about. The above worked for me as...

• I do not use Federated ( accesses data in tables of remote databases )
• INNODB is built into 5.6, no plugin required
• I do not use Blackhole ( accepts data but throws it away and does not store it )
• I do not use Archive ( storing large amounts of data without indexes in a very small footprint )