PDF (A4) - 40.5Mb
Man Pages (TGZ) - 259.5Kb
Man Pages (Zip) - 366.7Kb
Info (Gzip) - 4.1Mb
Info (Zip) - 4.1Mb
The following procedure applies toMyISAM tables. For information about steps to take when encounteringInnoDB table corruption, seeSection 1.6, “How to Report Bugs or Problems”.
If you encounter corruptedMyISAM tables or ifmysqld always fails after some update statements, you can test whether the issue is reproducible by doing the following:
Stop the MySQL daemon withmysqladmin shutdown.
Make a backup of the tables to guard against the very unlikely case that the repair does something bad.
Check all tables withmyisamchk -s database/*.MYI. Repair any corrupted tables withmyisamchk -r database/
table.MYI.Make a second backup of the tables.
Remove (or move away) any old log files from the MySQL data directory if you need more space.
Startmysqld with the binary log enabled. If you want to find a statement that crashesmysqld, you should start the server with the general query log enabled as well. SeeSection 7.4.3, “The General Query Log”, andSection 7.4.4, “The Binary Log”.
When you have gotten a crashed table, stop themysqld server.
Restore the backup.
Restart themysqld serverwithout the binary log enabled.
Re-execute the statements withmysqlbinlog binary-log-file | mysql. The binary log is saved in the MySQL database directory with the name
hostname-bin..NNNNNNIf the tables are corrupted again or you can getmysqld to die with the above command, you have found a reproducible bug. FTP the tables and the binary log to our bugs database using the instructions given inSection 1.6, “How to Report Bugs or Problems”. If you are a support customer, you can use the MySQL Customer Support Center (https://www.mysql.com/support/) to alert the MySQL team about the problem and have it fixed as soon as possible.
PDF (A4) - 40.5Mb
Man Pages (TGZ) - 259.5Kb
Man Pages (Zip) - 366.7Kb
Info (Gzip) - 4.1Mb
Info (Zip) - 4.1Mb