Skip navigation links

Additional languages
13.6.16.1 Troubleshooting InnoDB Data Dictionary Operations »
Section Navigation      [Toggle]

13.6.16. InnoDB Troubleshooting

[+/-]

13.6.16.1. Troubleshooting InnoDB Data Dictionary Operations

The following general guidelines apply to troubleshooting InnoDB problems:

  • When an operation fails or you suspect a bug, you should look at the MySQL server error log (see Section 5.2.2, “The Error Log”).

  • 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 --console option to direct the output to the console window.

  • Use the InnoDB Monitors to obtain information about a problem (see Section 13.6.10.1, “SHOW ENGINE INNODB STATUS and the InnoDB Monitors”). If the problem is performance-related, or your server appears to be hung, you should use innodb_monitor to print information about the internal state of InnoDB. If the problem is with locks, use innodb_lock_monitor. If the problem is in creation of tables or other data dictionary operations, use innodb_table_monitor to print the contents of the InnoDB internal data dictionary.

  • If you suspect that a table is corrupt, run CHECK TABLE on that table.

MySQL Enterprise.  The MySQL Enterprise Monitor provides a number of advisors specifically designed for monitoring InnoDB tables. In some cases, these advisors can anticipate potential problems. For more information, see http://www.mysql.com/products/enterprise/advisors.html.


User Comments

Posted by thomas collier on September 2 2005 7:48pm[Delete] [Edit]


The statement on this page "Use the InnoDB Monitors to obtain information about a problem". However you do not mention *how* to use these monitors. A simple example would help.

Posted by SeeQuelRun RunQuelRun on April 8 2006 10:36am[Delete] [Edit]

Installation with "innodb" as default database might not start.
It will show the error:

---
060408 12:31:45 [ERROR] Default storage engine (InnoDB) is not available
060408 12:31:45 [ERROR] Aborting

060408 12:31:45 [Note] mysqld: Shutdown complete
---

To solve this, add the following 2 lines manually to your my.ini file:
( My nickname is just for the credits ;-) )

#RunSQLRun: Start InnoDB database
innodb

Now your MySQL server will start the InnoDB.

Posted by Jeff Schwartz on May 13 2007 9:50pm[Delete] [Edit]

Beware: With innodb, CHECK TABLE tells you if the table is corrupted but cannot fix the corruption. Nor is there any other utility to do so.

Add your own comment.