(mysql.info.gz) InnoDB troubleshooting

(mysql.info.gz) InnoDB restrictions
 
 15.18 `InnoDB' Troubleshooting
 ==============================
 
    * A general rule is that when an operation fails or you suspect a
      bug, you should look at the MySQL server error log, which
      typically has a name something like `HOSTNAME.err', or possibly
      `mysql.err' on Windows.
 
    * When doing troubleshooting, it is usually best to run the MySQL
      server from the command prompt, not through the `mysqld_safe'
      wrapper or as a Windows service.  You will then see what `mysqld'
      prints to the command prompt window, and you have a better grasp
      of what is going on.  On Windows, you must start the server with
      the `--console' option to direct the output to the console window.
 
    * Use the `InnoDB' Monitors to obtain information about a problem.
      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 a table is corrupt, run `CHECK TABLE' on that table.
(mysql.info.gz) InnoDB troubleshooting

Menu
