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 READ and WRITE locks). Table maintenance operations can be time-consuming, particularly for large tables. If you use the --databases or --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 formysql_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 thatmysqlcheck 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 CHECK TABLE, REPAIR TABLE, 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”.

The MyISAM storage engine supports all four maintenance operations, so mysqlcheck can be used to perform any of them on MyISAM tables. Other storage engines do not necessarily support all operations. In such cases, an error message is displayed. For example, if test.t is a MEMORY table, an attempt to check it produces this result:

If mysqlcheck is unable to repair a table, see Section 2.19.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 withCHECK TABLE, but not repaired with REPAIR TABLE.


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:

If you do not name any tables following db_name or if you use the --databases or --all-databases option, entire databases are checked.

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 mysqlcheck named mysqlrepair, or make a symbolic link to mysqlcheck namedmysqlrepair. If you invoke mysqlrepair, it repairs tables.

The names shown in the following table can be used to change mysqlcheck default behavior.

mysqlrepairThe default option is --repair
mysqlanalyzeThe default option is --analyze
mysqloptimizeThe default option is --optimize

mysqlcheck supports the following options, which can be specified on the command line or in the [mysqlcheck]and [client] groups of an option file. For information about option files used by MySQL programs, seeSection 4.2.6, “Using Option Files”.

Table 4.4 mysqlcheck Options

–all-databasesCheck all tables in all databases
–all-in-1Execute a single statement for each database that names all the tables from that database
–analyzeAnalyze the tables
–auto-repairIf a checked table is corrupted, automatically fix it
–character-sets-dir=pathDirectory where character sets are installed
–checkCheck the tables for errors
–check-only-changedCheck only tables that have changed since the last check
–check-upgradeInvoke CHECK TABLE with the FOR UPGRADE option5.0.19
–compressCompress all information sent between client and server
–databasesProcess all tables in the named databases
–debug[=debug_options]Write a debugging log
–default-character-set=charset_nameSpecify default character set
–defaults-extra-file=file_nameRead option file in addition to usual option files
–defaults-file=file_nameRead only named option file
–defaults-group-suffix=strOption group suffix value5.0.10
–extendedCheck and repair tables
–fastCheck only tables that have not been closed properly
–forceContinue even if an SQL error occurs
–helpDisplay help message and exit
–host=host_nameConnect to MySQL server on given host
–medium-checkDo a check that is faster than an –extended operation
–no-defaultsRead no option files
–optimizeOptimize the tables
–password[=password]Password to use when connecting to server
–pipeOn Windows, connect to server using named pipe
–port=port_numTCP/IP port number to use for connection
–print-defaultsPrint defaults
–protocol=typeConnection protocol to use
–quickThe fastest method of checking
–repairPerform a repair that can fix almost anything except unique keys that are not unique
–shared-memory-base-name=nameThe name of shared memory to use for shared-memory connections
–silentSilent mode
–socket=pathFor connections to localhost, the Unix socket file to use
–sslEnable SSL for connection
–ssl-ca=file_namePath of file that contains list of trusted SSL CAs
–ssl-capath=dir_namePath of directory that contains trusted SSL CA certificates in PEM format
–ssl-cert=file_namePath of file that contains X509 certificate in PEM format
–ssl-cipher=cipher_listList of permitted ciphers to use for SSL encryption
–ssl-key=file_namePath of file that contains X509 key in PEM format
–ssl-verify-server-certVerify server Common Name value in its certificate against host name used when connecting to server5.0.23
–tablesOverrides the –databases or -B option
–use-frmFor repair operations on MyISAM tables
–user=user_name,MySQL user name to use when connecting to server
–verboseVerbose mode
–versionDisplay version information and exit