(mysql.info) innodb-troubleshooting

 
 14.2.17 `InnoDB' Troubleshooting
 --------------------------------

 
* innodb-troubleshooting-datadict  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, which is the file in the data
      directory that has a suffix of `.err'.
 
    * When troubleshooting, it is usually best to run the MySQL server
      from the command prompt, rather than through the `mysqld_safe'
      wrapper 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, 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
      (see  innodb-monitor). 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.

Info Catalog

(mysql.info) innodb-restrictions

(mysql.info) innodb

automatically generated byinfo2html

(mysql.info) innodb-troubleshooting

Menu