The following general guidelines apply to troubleshooting
When an operation fails or you suspect a bug, look at the MySQL server error log (see Section 5.4.2, “The Error Log”). Section B.3, “Server Error Codes and Messages” provides troubleshooting information for some of the common
InnoDB-specific errors that you may encounter.
Issues relating to the
InnoDBdata dictionary include failed
CREATE TABLEstatements (orphan table files), inability to open
.InnoDBfiles, and system cannot find the path specified errors. For information about these sorts of problems and errors, see Section 14.21.3, “Troubleshooting InnoDB Data Dictionary Operations”.
When troubleshooting, it is usually best to run the MySQL server from the command prompt, rather than through mysqld_safe or as a Windows service. You can then see what mysqld prints to the console, and so have a better grasp of what is going on. On Windows, start mysqld with the
--consoleoption to direct the output to the console window.
InnoDBMonitors to obtain information about a problem (see Section 14.17, “InnoDB Monitors”). If the problem is performance-related, or your server appears to be hung, you should enable the standard Monitor to print information about the internal state of
InnoDB. If the problem is with locks, enable the Lock Monitor. If the problem is in creation of tables or other data dictionary operations, enable the Table Monitor to print the contents of the
InnoDBinternal data dictionary. To see tablespace information enable the Tablespace Monitor.
InnoDBtemporarily enables standard
InnoDBMonitor output under the following conditions:
A long semaphore wait
InnoDBcannot find free blocks in the buffer pool
Over 67% of the buffer pool is occupied by lock heaps or the adaptive hash index
If you suspect that a table is corrupt, run
CHECK TABLEon that table.