The mysqlcheck client performs table maintenance: It checks, repairs, optimizes, or analyzes tables.
Each table is locked and therefore unavailable to other sessions
while it is being processed, although for check operations, the
table is locked with a
READ lock only (see
Section 13.3.5, “LOCK TABLES and UNLOCK TABLES Syntax”, for more information about
Table maintenance operations can be time-consuming, particularly
for large tables. If you use the
--all-databases option to
process all tables in one or more databases, an invocation of
mysqlcheck might take a long time. (This is
also true for mysql_upgrade because that
program invokes mysqlcheck to check all
tables and repair them if necessary.)
mysqlcheck is similar in function to myisamchk, but works differently. The main operational difference is that mysqlcheck must be used when the mysqld server is running, whereas myisamchk should be used when it is not. The benefit of using mysqlcheck is that you do not have to stop the server to perform table maintenance.
mysqlcheck uses the SQL statements
ANALYZE TABLE, and
OPTIMIZE TABLE in a convenient
way for the user. It determines which statements to use for the
operation you want to perform, and then sends the statements to
the server to be executed. For details about which storage
engines each statement works with, see the descriptions for
those statements in Section 13.7.2, “Table Maintenance Statements”.
MyISAM storage engine supports all four
maintenance operations, so mysqlcheck can be
used to perform any of them on
Other storage engines do not necessarily support all operations.
In such cases, an error message is displayed. For example, if
test.t is a
an attempt to check it produces this result:
mysqlcheck test ttest.t note : The storage engine for the table doesn't support check
If mysqlcheck is unable to repair a table,
see Section 2.13.4, “Rebuilding or Repairing Tables or Indexes” for manual table repair
strategies. This will be the case, for example, for
InnoDB tables, which can be checked with
CHECK TABLE, but not repaired
The use of mysqlcheck with partitioned tables is not supported before MySQL 5.1.27.
It is best to make a backup of a table before performing a table repair operation; under some circumstances the operation might cause data loss. Possible causes include but are not limited to file system errors.
There are three general ways to invoke mysqlcheck:
mysqlcheck has a special feature compared to
other client programs. The default behavior of checking tables
--check) can be changed by
renaming the binary. If you want to have a tool that repairs
tables by default, you should just make a copy of
mysqlrepair, or make a symbolic link to
mysqlrepair. If you invoke
mysqlrepair, it repairs tables.
The names shown in the following table can be used to change mysqlcheck default behavior.
|mysqlrepair||The default option is |
|mysqlanalyze||The default option is |
|mysqloptimize||The default option is |
mysqlcheck supports the following options,
which can be specified on the command line or in the
groups of an option file. For information about option files
used by MySQL programs, see Section 4.2.6, “Using Option Files”.
|--all-databases||Check all tables in all databases|
|--all-in-1||Execute a single statement for each database that names all the tables from that database|
|--analyze||Analyze the tables|
|--auto-repair||If a checked table is corrupted, automatically fix it|
|--bind-address||Use specified network interface to connect to MySQL Server||5.1.22-ndb-6.3.4|
|--character-sets-dir||Directory where character sets are installed|
|--check||Check the tables for errors|
|--check-only-changed||Check only tables that have changed since the last check|
|--check-upgrade||Invoke CHECK TABLE with the FOR UPGRADE option||5.1.7|
|--compress||Compress all information sent between client and server|
|--databases||Interpret all arguments as database names|
|--debug||Write debugging log|
|--debug-check||Print debugging information when program exits||5.1.21|
|--debug-info||Print debugging information, memory, and CPU statistics when program exits||5.1.14|
|--default-character-set||Specify default character set|
|--defaults-extra-file||Read named option file in addition to usual option files|
|--defaults-file||Read only named option file|
|--defaults-group-suffix||Option group suffix value|
|--extended||Check and repair tables|
|--fast||Check only tables that have not been closed properly|
|--fix-db-names||Convert database names to 5.1 format||5.1.7|
|--fix-table-names||Convert table names to 5.1 format||5.1.7|
|--force||Continue even if an SQL error occurs|
|--help||Display help message and exit|
|--host||Connect to MySQL server on given host|
|--medium-check||Do a check that is faster than an --extended operation|
|--no-defaults||Read no option files|
|--optimize||Optimize the tables|
|--password||Password to use when connecting to server|
|--pipe||On Windows, connect to server using named pipe|
|--port||TCP/IP port number to use for connection|
|--print-defaults||Print default options|
|--protocol||Connection protocol to use|
|--quick||The fastest method of checking|
|--repair||Perform a repair that can fix almost anything except unique keys that are not unique|
|--shared-memory-base-name||The name of shared memory to use for shared-memory connections|
|--socket||For connections to localhost, the Unix socket file to use|
|--ssl||Enable SSL for connection|
|--ssl-ca||Path of file that contains list of trusted SSL CAs|
|--ssl-capath||Path of directory that contains trusted SSL CA certificates in PEM format|
|--ssl-cert||Path of file that contains X509 certificate in PEM format|
|--ssl-cipher||List of permitted ciphers to use for SSL encryption|
|--ssl-key||Path of file that contains X509 key in PEM format|
|--ssl-verify-server-cert||Verify Common Name value in server certificate against host name used when connecting to server||5.1.11|
|--tables||Overrides the --databases or -B option|
|--use-frm||For repair operations on MyISAM tables|
|--user||MySQL user name to use when connecting to server|
|--version||Display version information and exit|
|--write-binlog||Log ANALYZE, OPTIMIZE, REPAIR statements to binary log. --skip-write-binlog adds NO_WRITE_TO_BINLOG to these statements.||5.1.18|
Display a help message and exit.
Check all tables in all databases. This is the same as using the
--databasesoption and naming all the databases on the command line.
Instead of issuing a statement for each table, execute a single statement for each database that names all the tables from that database to be processed.
Analyze the tables.
If a checked table is corrupted, automatically fix it. Any necessary repairs are done after all tables have been checked.
On a computer having multiple network interfaces, use this option to select which interface to use for connecting to the MySQL server.
This option is supported only in the version of mysqlcheck that is supplied with MySQL Cluster, beginning with MySQL Cluster NDB 6.3.4. It is not available in standard MySQL 5.1 releases.
The directory where character sets are installed. See Section 10.5, “Character Set Configuration”.
Check the tables for errors. This is the default operation.
Check only tables that have changed since the last check or that have not been closed properly.
CHECK TABLEwith the
FOR UPGRADEoption to check tables for incompatibilities with the current version of the server. This option automatically enables the
--check-upgradewas added in MySQL 5.1.7.
Compress all information sent between the client and the server if both support compression.
Process all tables in the named databases. Normally, mysqlcheck treats the first name argument on the command line as a database name and any following names as table names. With this option, it treats all name arguments as database names.
Write a debugging log. A typical
d:t:o,. The default is
Print some debugging information when the program exits. This option was added in MySQL 5.1.21.
Print debugging information and memory and CPU usage statistics when the program exits. This option was added in MySQL 5.1.14.
charset_nameas the default character set. See Section 10.5, “Character Set Configuration”.
Read this option file after the global option file but (on Unix) before the user option file. If the file does not exist or is otherwise inaccessible, an error occurs.
file_nameis the full path name to the file.
Use only the given option file. If the file does not exist or is otherwise inaccessible, an error occurs.
file_nameis the full path name to the file.
Read not only the usual option groups, but also groups with the usual names and a suffix of
str. For example, mysqlcheck normally reads the
[mysqlcheck]groups. If the
--defaults-group-suffix=_otheroption is given, mysqlcheck also reads the
If you are using this option to check tables, it ensures that they are 100% consistent but takes a long time.
If you are using this option to repair tables, it runs an extended repair that may not only take a long time to execute, but may produce a lot of garbage rows also!
Check only tables that have not been closed properly.
Convert database names to 5.1 format. Only database names that contain special characters are affected. This option was added in MySQL 5.1.7.
Convert table names to 5.1 format. Only table names that contain special characters are affected. This option was added in MySQL 5.1.7. As of MySQL 5.1.23, this option also applies to views.
Continue even if an SQL error occurs.
Connect to the MySQL server on the given host.
Do a check that is faster than an
--extendedoperation. This finds only 99.99% of all errors, which should be good enough in most cases.
Do not read any option files. If program startup fails due to reading unknown options from an option file,
--no-defaultscan be used to prevent them from being read.
Optimize the tables.
The password to use when connecting to the server. If you use the short option form (
-p), you cannot have a space between the option and the password. If you omit the
passwordvalue following the
-poption on the command line, mysqlcheck prompts for one.
Specifying a password on the command line should be considered insecure. See Section 220.127.116.11, “End-User Guidelines for Password Security”. You can use an option file to avoid giving the password on the command line.
On Windows, connect to the server using a named pipe. This option applies only if the server supports named-pipe connections.
The TCP/IP port number to use for the connection.
Print the program name and all options that it gets from option files.
The connection protocol to use for connecting to the server. It is useful when the other connection parameters normally would cause a protocol to be used other than the one you want. For details on the permissible values, see Section 4.2.2, “Connecting to the MySQL Server”.
If you are using this option to check tables, it prevents the check from scanning the rows to check for incorrect links. This is the fastest check method.
If you are using this option to repair tables, it tries to repair only the index tree. This is the fastest repair method.
Perform a repair that can fix almost anything except unique keys that are not unique.
On Windows, the shared-memory name to use, for connections made using shared memory to a local server. The default value is
MYSQL. The shared-memory name is case sensitive.
The server must be started with the
--shared-memoryoption to enable shared-memory connections.
Silent mode. Print only error messages.
For connections to
localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use.
-Boption. All name arguments following the option are regarded as table names.
For repair operations on
MyISAMtables, get the table structure from the
.frmfile so that the table can be repaired even if the
.MYIheader is corrupted.
The MySQL user name to use when connecting to the server.
Verbose mode. Print information about the various stages of program operation.
Display version information and exit.
This option is enabled by default, so that
OPTIMIZE TABLE, and
REPAIR TABLEstatements generated by mysqlcheck are written to the binary log. Use
NO_WRITE_TO_BINLOGto be added to the statements so that they are not logged. Use the
--skip-write-binlogwhen these statements should not be sent to replication slaves or run when using the binary logs for recovery from backup. This option was added in MySQL 5.1.18.