SEARCH
NEW RPMS
DIRECTORIES
ABOUT
FAQ
VARIOUS
BLOG
DONATE


YUM REPOSITORY

 
 

MAN page from RedHat EL 5 MySQL-client-community-5.1.72-1.rhel5.x86_64.rpm

\FBMYSQLCHECK\FR

Section: MySQL Database System (1)
Updated: 09/09/2013
Index 

NAME

mysqlcheck - a table maintenance program 

SYNOPSIS

mysqlcheck [options] [db_name [tbl_name ...]]
 

DESCRIPTION

Themysqlcheckclient 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 aREADlock only (seeSection 13.3.5, lqLOCK TABLES and UNLOCK TABLES Syntaxrq, for more information aboutREADandWRITElocks). Table maintenance operations can be time-consuming, particularly for large tables. If you use the--databasesor--all-databasesoption to process all tables in one or more databases, an invocation ofmysqlcheckmight take a long time. (This is also true formysql_upgradebecause that program invokesmysqlcheckto check all tables and repair them if necessary.)

mysqlcheckis similar in function tomyisamchk, but works differently. The main operational difference is thatmysqlcheckmust be used when themysqldserver is running, whereasmyisamchkshould be used when it is not. The benefit of usingmysqlcheckis that you do not have to stop the server to perform table maintenance.

mysqlcheckuses the SQL statementsCHECK TABLE,REPAIR TABLE,ANALYZE TABLE, andOPTIMIZE TABLEin 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 inSection 13.7.2, lqTable Maintenance Statementsrq.

TheMyISAMstorage engine supports all four maintenance operations, somysqlcheckcan be used to perform any of them onMyISAMtables. Other storage engines do not necessarily support all operations. In such cases, an error message is displayed. For example, iftest.tis aMEMORYtable, an attempt to check it produces this result:

shell> mysqlcheck test ttest.tnote     : The storage engine for the table doesn't support check

Ifmysqlcheckis unable to repair a table, seeSection 2.13.4, lqRebuilding or Repairing Tables or Indexesrqfor manual table repair strategies. This will be the case, for example, forInnoDBtables, which can be checked withCHECK TABLE, but not repaired withREPAIR TABLE.

The use ofmysqlcheckwith partitioned tables is not supported before MySQL 5.1.27.


Caution

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 invokemysqlcheck:

shell> mysqlcheck [options] db_name [tbl_name ...]shell> mysqlcheck [options] --databases db_name ...shell> mysqlcheck [options] --all-databases

If you do not name any tables followingdb_nameor if you use the--databasesor--all-databasesoption, entire databases are checked.

mysqlcheckhas 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 ofmysqlchecknamedmysqlrepair, or make a symbolic link tomysqlchecknamedmysqlrepair. If you invokemysqlrepair, it repairs tables.

The names shown in the following table can be used to changemysqlcheckdefault behavior.
CommandMeaning
mysqlrepairThe default option is --repair
mysqlanalyzeThe default option is --analyze
mysqloptimizeThe default option is --optimize

mysqlchecksupports the following options, which can be specified on the command line or in the[mysqlcheck]and[client]groups of an option file.mysqlcheckalso supports the options for processing option files described atSection 4.2.3.4, lqCommand-Line Options that Affect Option-File Handlingrq.

*--help,-?

Display a help message and exit.

*--all-databases,-A

Check all tables in all databases. This is the same as using the--databasesoption and naming all the databases on the command line.

*--all-in-1,-1

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,-a

Analyze the tables.

*--auto-repair

If a checked table is corrupted, automatically fix it. Any necessary repairs are done after all tables have been checked.

*--bind-address=ip_address

On a computer having multiple network interfaces, this option can be used to select which interface is employed when connecting to the MySQL server.

This option is supported only in the version ofmysqlcheckthat is supplied with MySQL Cluster, beginning with MySQL Cluster NDB 6.3.4. It is not available in standard MySQL 5.1 releases.

*--character-sets-dir=path

The directory where character sets are installed. SeeSection 10.5, lqCharacter Set Configurationrq.

*--check,-c

Check the tables for errors. This is the default operation.

*--check-only-changed,-C

Check only tables that have changed since the last check or that have not been closed properly.

*--check-upgrade,-g

InvokeCHECK TABLEwith theFOR UPGRADEoption to check tables for incompatibilities with the current version of the server. This option automatically enables the--fix-db-namesand--fix-table-namesoptions.--check-upgradewas added in MySQL 5.1.7.

*--compress

Compress all information sent between the client and the server if both support compression.

*--databases,-B

Process all tables in the named databases. Normally,mysqlchecktreats the first name argument on the command line as a database name and following names as table names. With this option, it treats all name arguments as database names.

*--debug[=debug_options],-# [debug_options]

Write a debugging log. A typicaldebug_optionsstring is'd:t:o,file_name'. The default is'd:t:o'.

*--debug-check

Print some debugging information when the program exits. This option was added in MySQL 5.1.21.

*--debug-info

Print debugging information and memory and CPU usage statistics when the program exits. This option was added in MySQL 5.1.14.

*--default-character-set=charset_name

Usecharset_nameas the default character set. SeeSection 10.5, lqCharacter Set Configurationrq.

*--extended,-e

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!

*--fast,-F

Check only tables that have not been closed properly.

*--fix-db-names

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.

*--fix-table-names

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.

*--force,-f

Continue even if an SQL error occurs.

*--host=host_name,-h host_name

Connect to the MySQL server on the given host.

*--medium-check,-m

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.

*--optimize,-o

Optimize the tables.

*--password[=password],-p[password]

The password to use when connecting to the server. If you use the short option form (-p), youcannothave a space between the option and the password. If you omit thepasswordvalue following the--passwordor-poption on the command line,mysqlcheckprompts for one.

Specifying a password on the command line should be considered insecure. SeeSection 6.1.2.1, lqEnd-User Guidelines for Password Securityrq. You can use an option file to avoid giving the password on the command line.

*--pipe,-W

On Windows, connect to the server using a named pipe. This option applies only if the server supports named-pipe connections.

*--port=port_num,-P port_num

The TCP/IP port number to use for the connection.

*--protocol={TCP|SOCKET|PIPE|MEMORY}

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, seeSection 4.2.2, lqConnecting to the MySQL Serverrq.

*--quick,-q

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.

*--repair,-r

Perform a repair that can fix almost anything except unique keys that are not unique.

*--silent,-s

Silent mode. Print only error messages.

*--socket=path,-S path

For connections tolocalhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use.

*--ssl*

Options that begin with--sslspecify whether to connect to the server using SSL and indicate where to find SSL keys and certificates. SeeSection 6.3.6.4, lqSSL Command Optionsrq.

*--tables

Override the--databasesor-Boption. All name arguments following the option are regarded as table names.

*--use-frm

For repair operations onMyISAMtables, get the table structure from the.frmfile so that the table can be repaired even if the.MYIheader is corrupted.

*--user=user_name,-u user_name

The MySQL user name to use when connecting to the server.

*--verbose,-v

Verbose mode. Print information about the various stages of program operation.

*--version,-V

Display version information and exit.

*--write-binlog

This option is enabled by default, so thatANALYZE TABLE,OPTIMIZE TABLE, andREPAIR TABLEstatements generated bymysqlcheckare written to the binary log. Use--skip-write-binlogto causeNO_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.

 

COPYRIGHT


Copyright © 1997, 2013, Oracle and/or its affiliates. All rights reserved.

This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.

This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with the program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA or see http://www.gnu.org/licenses/.

 

SEE ALSO

For more information, please refer to the MySQL Reference Manual,which may already be installed locally and which is also availableonline at http://dev.mysql.com/doc/. 

AUTHOR

Oracle Corporation (http://dev.mysql.com/).


 

Index

NAME
SYNOPSIS
DESCRIPTION
COPYRIGHT
SEE ALSO
AUTHOR

This document was created byman2html,using the manual pages.