{
    "mode": "man",
    "parameter": "mysqlanalyze",
    "section": "1",
    "url": "https://www.chedong.com/phpMan.php/man/mysqlanalyze/1/json",
    "generated": "2026-05-30T06:08:38Z",
    "synopsis": "mysqlcheck [options] [dbname [tblname ...]]",
    "sections": {
        "NAME": {
            "content": "mysqlcheck - a table maintenance program\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "mysqlcheck [options] [dbname [tblname ...]]\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "The mysqlcheck client performs table maintenance: It checks, repairs, optimizes, or analyzes\ntables.\n\nEach table is locked and therefore unavailable to other sessions while it is being processed,\nalthough for check operations, the table is locked with a READ lock only (see Section 15.3.6,\n“LOCK TABLES and UNLOCK TABLES Statements”, for more information about READ and WRITE locks).\nTable maintenance operations can be time-consuming, particularly for large tables. If you use\nthe --databases or --all-databases option to process all tables in one or more databases, an\ninvocation of mysqlcheck might take a long time. (This is also true for the MySQL upgrade\nprocedure if it determines that table checking is needed because it processes tables the same\nway.)\n\nmysqlcheck must be used when the mysqld server is running, which means that you do not have\nto stop the server to perform table maintenance.\n\nmysqlcheck uses the SQL statements CHECK TABLE, REPAIR TABLE, ANALYZE TABLE, and OPTIMIZE\nTABLE in a convenient way for the user. It determines which statements to use for the\noperation you want to perform, and then sends the statements to the server to be executed.\nFor details about which storage engines each statement works with, see the descriptions for\nthose statements in Section 15.7.3, “Table Maintenance Statements”.\n\nAll storage engines do not necessarily support all four maintenance operations. In such\ncases, an error message is displayed. For example, if test.t is an MEMORY table, an attempt\nto check it produces this result:\n\n$> mysqlcheck test t\ntest.t\nnote     : The storage engine for the table doesn't support check\n\nIf mysqlcheck is unable to repair a table, see Section 3.14, “Rebuilding or Repairing Tables\nor Indexes” for manual table repair strategies. This is the case, for example, for InnoDB\ntables, which can be checked with CHECK TABLE, but not repaired with REPAIR TABLE.\n\nCaution\nIt is best to make a backup of a table before performing a table repair operation; under\nsome circumstances the operation might cause data loss. Possible causes include but are\nnot limited to file system errors.\n\nThere are three general ways to invoke mysqlcheck:\n\nmysqlcheck [options] dbname [tblname ...]\nmysqlcheck [options] --databases dbname ...\nmysqlcheck [options] --all-databases\n\nIf you do not name any tables following dbname or if you use the --databases or\n--all-databases option, entire databases are checked.\n\nmysqlcheck has a special feature compared to other client programs. The default behavior of\nchecking tables (--check) can be changed by renaming the binary. If you want to have a tool\nthat repairs tables by default, you should just make a copy of mysqlcheck named mysqlrepair,\nor make a symbolic link to mysqlcheck named mysqlrepair. If you invoke mysqlrepair, it\nrepairs tables.\n\nThe names shown in the following table can be used to change mysqlcheck default behavior.\n\n┌──────────────┬──────────────────────────────────┐\n│Command       │ Meaning                          │\n├──────────────┼──────────────────────────────────┤\n│mysqlrepair   │ The default option is --repair   │\n├──────────────┼──────────────────────────────────┤\n│mysqlanalyze  │ The default option is --analyze  │\n├──────────────┼──────────────────────────────────┤\n│mysqloptimize │ The default option is --optimize │\n└──────────────┴──────────────────────────────────┘\n\nmysqlcheck supports the following options, which can be specified on the command line or in\nthe [mysqlcheck] and [client] groups of an option file. For information about option files\nused by MySQL programs, see Section 6.2.2.2, “Using Option Files”.\n\n•   --help, -?\n\n┌────────────────────┬────────┐\n│Command-Line Format │ --help │\n└────────────────────┴────────┘\nDisplay a help message and exit.\n\n•   --all-databases, -A\n\n┌────────────────────┬─────────────────┐\n│Command-Line Format │ --all-databases │\n└────────────────────┴─────────────────┘\nCheck all tables in all databases. This is the same as using the --databases option and\nnaming all the databases on the command line, except that the INFORMATIONSCHEMA and\nperformanceschema databases are not checked. They can be checked by explicitly naming\nthem with the --databases option.\n\n•   --all-in-1, -1\n\n┌────────────────────┬────────────┐\n│Command-Line Format │ --all-in-1 │\n└────────────────────┴────────────┘\nInstead of issuing a statement for each table, execute a single statement for each\ndatabase that names all the tables from that database to be processed.\n\n•   --analyze, -a\n\n┌────────────────────┬───────────┐\n│Command-Line Format │ --analyze │\n└────────────────────┴───────────┘\nAnalyze the tables.\n\n•   --auto-repair\n\n┌────────────────────┬───────────────┐\n│Command-Line Format │ --auto-repair │\n└────────────────────┴───────────────┘\nIf a checked table is corrupted, automatically fix it. Any necessary repairs are done\nafter all tables have been checked.\n\n•   --bind-address=ipaddress\n\n┌────────────────────┬───────────────────────────┐\n│Command-Line Format │ --bind-address=ipaddress │\n└────────────────────┴───────────────────────────┘\nOn a computer having multiple network interfaces, use this option to select which\ninterface to use for connecting to the MySQL server.\n\n•   --character-sets-dir=dirname\n\n┌────────────────────┬───────────────────────────────┐\n│Command-Line Format │ --character-sets-dir=dirname │\n├────────────────────┼───────────────────────────────┤\n│Type                │ Directory name                │\n└────────────────────┴───────────────────────────────┘\nThe directory where character sets are installed. See Section 12.15, “Character Set\nConfiguration”.\n\n•   --check, -c\n\n┌────────────────────┬─────────┐\n│Command-Line Format │ --check │\n└────────────────────┴─────────┘\nCheck the tables for errors. This is the default operation.\n\n•   --check-only-changed, -C\n\n┌────────────────────┬──────────────────────┐\n│Command-Line Format │ --check-only-changed │\n└────────────────────┴──────────────────────┘\nCheck only tables that have changed since the last check or that have not been closed\nproperly.\n\n•   --check-upgrade, -g\n\n┌────────────────────┬─────────────────┐\n│Command-Line Format │ --check-upgrade │\n└────────────────────┴─────────────────┘\nInvoke CHECK TABLE with the FOR UPGRADE option to check tables for incompatibilities with\nthe current version of the server.\n\n•   --compress\n\n┌────────────────────┬───────────────────────┐\n│Command-Line Format │ --compress[={OFF|ON}] │\n├────────────────────┼───────────────────────┤\n│Deprecated          │ 8.0.18                │\n├────────────────────┼───────────────────────┤\n│Type                │ Boolean               │\n├────────────────────┼───────────────────────┤\n│Default Value       │ OFF                   │\n└────────────────────┴───────────────────────┘\nCompress all information sent between the client and the server if possible. See\nSection 6.2.8, “Connection Compression Control”.\n\nAs of MySQL 8.0.18, this option is deprecated. Expect it to be removed in a future\nversion of MySQL. See the section called “Configuring Legacy Connection Compression”.\n\n•   --compression-algorithms=value\n\n┌────────────────────┬────────────────────────────────┐\n│Command-Line Format │ --compression-algorithms=value │\n├────────────────────┼────────────────────────────────┤\n│Introduced          │ 8.0.18                         │\n├────────────────────┼────────────────────────────────┤\n│Type                │ Set                            │\n├────────────────────┼────────────────────────────────┤\n│Default Value       │ uncompressed                   │\n├────────────────────┼────────────────────────────────┤\n│Valid Values        │                                │\n│                    │            zlib                │\n│                    │                                │\n│                    │            zstd                │\n│                    │                                │\n│                    │            uncompressed        │\n└────────────────────┴────────────────────────────────┘\nThe permitted compression algorithms for connections to the server. The available\nalgorithms are the same as for the protocolcompressionalgorithms system variable. The\ndefault value is uncompressed.\n\nFor more information, see Section 6.2.8, “Connection Compression Control”.\n\nThis option was added in MySQL 8.0.18.\n\n•   --databases, -B\n\n┌────────────────────┬─────────────┐\n│Command-Line Format │ --databases │\n└────────────────────┴─────────────┘\nProcess all tables in the named databases. Normally, mysqlcheck treats the first name\nargument on the command line as a database name and any following names as table names.\nWith this option, it treats all name arguments as database names.\n\n•   --debug[=debugoptions], -# [debugoptions]\n\n┌────────────────────┬─────────────────────────┐\n│Command-Line Format │ --debug[=debugoptions] │\n├────────────────────┼─────────────────────────┤\n│Type                │ String                  │\n├────────────────────┼─────────────────────────┤\n│Default Value       │ d:t:o                   │\n└────────────────────┴─────────────────────────┘\nWrite a debugging log. A typical debugoptions string is d:t:o,filename. The default is\nd:t:o.\n\nThis option is available only if MySQL was built using WITHDEBUG. MySQL release binaries\nprovided by Oracle are not built using this option.\n\n•   --debug-check\n\n┌────────────────────┬───────────────┐\n│Command-Line Format │ --debug-check │\n├────────────────────┼───────────────┤\n│Type                │ Boolean       │\n├────────────────────┼───────────────┤\n│Default Value       │ FALSE         │\n└────────────────────┴───────────────┘\nPrint some debugging information when the program exits.\n\nThis option is available only if MySQL was built using WITHDEBUG. MySQL release binaries\nprovided by Oracle are not built using this option.\n\n•   --debug-info\n\n┌────────────────────┬──────────────┐\n│Command-Line Format │ --debug-info │\n├────────────────────┼──────────────┤\n│Type                │ Boolean      │\n├────────────────────┼──────────────┤\n│Default Value       │ FALSE        │\n└────────────────────┴──────────────┘\nPrint debugging information and memory and CPU usage statistics when the program exits.\n\nThis option is available only if MySQL was built using WITHDEBUG. MySQL release binaries\nprovided by Oracle are not built using this option.\n\n•   --default-character-set=charsetname\n\n┌────────────────────┬──────────────────────┐\n│Command-Line Format │ --default-character- │\n│                    │ set=charsetname     │\n├────────────────────┼──────────────────────┤\n│Type                │ String               │\n└────────────────────┴──────────────────────┘\nUse charsetname as the default character set. See Section 12.15, “Character Set\nConfiguration”.\n\n•   --defaults-extra-file=filename\n\n┌────────────────────┬─────────────────────────────────┐\n│Command-Line Format │ --defaults-extra-file=filename │\n├────────────────────┼─────────────────────────────────┤\n│Type                │ File name                       │\n└────────────────────┴─────────────────────────────────┘\nRead this option file after the global option file but (on Unix) before the user option\nfile. If the file does not exist or is otherwise inaccessible, an error occurs. If\nfilename is not an absolute path name, it is interpreted relative to the current\ndirectory.\n\nFor additional information about this and other option-file options, see Section 6.2.2.3,\n“Command-Line Options that Affect Option-File Handling”.\n\n•   --defaults-file=filename\n\n┌────────────────────┬───────────────────────────┐\n│Command-Line Format │ --defaults-file=filename │\n├────────────────────┼───────────────────────────┤\n│Type                │ File name                 │\n└────────────────────┴───────────────────────────┘\nUse only the given option file. If the file does not exist or is otherwise inaccessible,\nan error occurs. If filename is not an absolute path name, it is interpreted relative to\nthe current directory.\n\nException: Even with --defaults-file, client programs read .mylogin.cnf.\n\nFor additional information about this and other option-file options, see Section 6.2.2.3,\n“Command-Line Options that Affect Option-File Handling”.\n\n•   --defaults-group-suffix=str\n\n┌────────────────────┬─────────────────────────────┐\n│Command-Line Format │ --defaults-group-suffix=str │\n├────────────────────┼─────────────────────────────┤\n│Type                │ String                      │\n└────────────────────┴─────────────────────────────┘\nRead not only the usual option groups, but also groups with the usual names and a suffix\nof str. For example, mysqlcheck normally reads the [client] and [mysqlcheck] groups. If\nthis option is given as --defaults-group-suffix=other, mysqlcheck also reads the\n[clientother] and [mysqlcheckother] groups.\n\nFor additional information about this and other option-file options, see Section 6.2.2.3,\n“Command-Line Options that Affect Option-File Handling”.\n\n•   --extended, -e\n\n┌────────────────────┬────────────┐\n│Command-Line Format │ --extended │\n└────────────────────┴────────────┘\nIf you are using this option to check tables, it ensures that they are 100% consistent\nbut takes a long time.\n\nIf you are using this option to repair tables, it runs an extended repair that may not\nonly take a long time to execute, but may produce a lot of garbage rows also!\n\n•   --default-auth=plugin\n\n┌────────────────────┬───────────────────────┐\n│Command-Line Format │ --default-auth=plugin │\n├────────────────────┼───────────────────────┤\n│Type                │ String                │\n└────────────────────┴───────────────────────┘\nA hint about which client-side authentication plugin to use. See Section 8.2.17,\n“Pluggable Authentication”.\n\n•   --enable-cleartext-plugin\n\n┌────────────────────┬───────────────────────────┐\n│Command-Line Format │ --enable-cleartext-plugin │\n├────────────────────┼───────────────────────────┤\n│Type                │ Boolean                   │\n├────────────────────┼───────────────────────────┤\n│Default Value       │ FALSE                     │\n└────────────────────┴───────────────────────────┘\nEnable the mysqlclearpassword cleartext authentication plugin. (See Section 8.4.1.4,\n“Client-Side Cleartext Pluggable Authentication”.)\n\n•   --fast, -F\n\n┌────────────────────┬────────┐\n│Command-Line Format │ --fast │\n└────────────────────┴────────┘\nCheck only tables that have not been closed properly.\n\n•   --force, -f\n\n┌────────────────────┬─────────┐\n│Command-Line Format │ --force │\n└────────────────────┴─────────┘\nContinue even if an SQL error occurs.\n\n•   --get-server-public-key\n\n┌────────────────────┬─────────────────────────┐\n│Command-Line Format │ --get-server-public-key │\n├────────────────────┼─────────────────────────┤\n│Type                │ Boolean                 │\n└────────────────────┴─────────────────────────┘\nRequest from the server the public key required for RSA key pair-based password exchange.\nThis option applies to clients that authenticate with the cachingsha2password\nauthentication plugin. For that plugin, the server does not send the public key unless\nrequested. This option is ignored for accounts that do not authenticate with that plugin.\nIt is also ignored if RSA-based password exchange is not used, as is the case when the\nclient connects to the server using a secure connection.\n\nIf --server-public-key-path=filename is given and specifies a valid public key file, it\ntakes precedence over --get-server-public-key.\n\nFor information about the cachingsha2password plugin, see Section 8.4.1.2, “Caching\nSHA-2 Pluggable Authentication”.\n\n•   --host=hostname, -h hostname\n\n┌────────────────────┬──────────────────┐\n│Command-Line Format │ --host=hostname │\n├────────────────────┼──────────────────┤\n│Type                │ String           │\n├────────────────────┼──────────────────┤\n│Default Value       │ localhost        │\n└────────────────────┴──────────────────┘\nConnect to the MySQL server on the given host.\n\n•   --login-path=name\n\n┌────────────────────┬───────────────────┐\n│Command-Line Format │ --login-path=name │\n├────────────────────┼───────────────────┤\n│Type                │ String            │\n└────────────────────┴───────────────────┘\nRead options from the named login path in the .mylogin.cnf login path file. A “login\npath” is an option group containing options that specify which MySQL server to connect to\nand which account to authenticate as. To create or modify a login path file, use the\nmysqlconfigeditor utility. See mysqlconfigeditor(1).\n\nFor additional information about this and other option-file options, see Section 6.2.2.3,\n“Command-Line Options that Affect Option-File Handling”.\n\n•   --medium-check, -m\n\n┌────────────────────┬────────────────┐\n│Command-Line Format │ --medium-check │\n└────────────────────┴────────────────┘\nDo a check that is faster than an --extended operation. This finds only 99.99% of all\nerrors, which should be good enough in most cases.\n\n•   --no-defaults\n\n┌────────────────────┬───────────────┐\n│Command-Line Format │ --no-defaults │\n└────────────────────┴───────────────┘\nDo not read any option files. If program startup fails due to reading unknown options\nfrom an option file, --no-defaults can be used to prevent them from being read.\n\nThe exception is that the .mylogin.cnf file is read in all cases, if it exists. This\npermits passwords to be specified in a safer way than on the command line even when\n--no-defaults is used. To create .mylogin.cnf, use the mysqlconfigeditor utility. See\nmysqlconfigeditor(1).\n\nFor additional information about this and other option-file options, see Section 6.2.2.3,\n“Command-Line Options that Affect Option-File Handling”.\n\n•   --optimize, -o\n\n┌────────────────────┬────────────┐\n│Command-Line Format │ --optimize │\n└────────────────────┴────────────┘\nOptimize the tables.\n\n•   --password[=password], -p[password]\n\n┌────────────────────┬───────────────────────┐\n│Command-Line Format │ --password[=password] │\n├────────────────────┼───────────────────────┤\n│Type                │ String                │\n└────────────────────┴───────────────────────┘\nThe password of the MySQL account used for connecting to the server. The password value\nis optional. If not given, mysqlcheck prompts for one. If given, there must be no space\nbetween --password= or -p and the password following it. If no password option is\nspecified, the default is to send no password.\n\nSpecifying a password on the command line should be considered insecure. To avoid giving\nthe password on the command line, use an option file. See Section 8.1.2.1, “End-User\nGuidelines for Password Security”.\n\nTo explicitly specify that there is no password and that mysqlcheck should not prompt for\none, use the --skip-password option.\n\n•   --password1[=passval] The password for multifactor authentication factor 1 of the MySQL\naccount used for connecting to the server. The password value is optional. If not given,\nmysqlcheck prompts for one. If given, there must be no space between --password1= and the\npassword following it. If no password option is specified, the default is to send no\npassword.\n\nSpecifying a password on the command line should be considered insecure. To avoid giving\nthe password on the command line, use an option file. See Section 8.1.2.1, “End-User\nGuidelines for Password Security”.\n\nTo explicitly specify that there is no password and that mysqlcheck should not prompt for\none, use the --skip-password1 option.\n\n--password1 and --password are synonymous, as are --skip-password1 and --skip-password.\n\n•   --password2[=passval] The password for multifactor authentication factor 2 of the MySQL\naccount used for connecting to the server. The semantics of this option are similar to\nthe semantics for --password1; see the description of that option for details.\n\n•   --password3[=passval] The password for multifactor authentication factor 3 of the MySQL\naccount used for connecting to the server. The semantics of this option are similar to\nthe semantics for --password1; see the description of that option for details.\n\n•   --pipe, -W\n\n┌────────────────────┬────────┐\n│Command-Line Format │ --pipe │\n├────────────────────┼────────┤\n│Type                │ String │\n└────────────────────┴────────┘\nOn Windows, connect to the server using a named pipe. This option applies only if the\nserver was started with the namedpipe system variable enabled to support named-pipe\nconnections. In addition, the user making the connection must be a member of the Windows\ngroup specified by the namedpipefullaccessgroup system variable.\n\n•   --plugin-dir=dirname\n\n┌────────────────────┬───────────────────────┐\n│Command-Line Format │ --plugin-dir=dirname │\n├────────────────────┼───────────────────────┤\n│Type                │ Directory name        │\n└────────────────────┴───────────────────────┘\nThe directory in which to look for plugins. Specify this option if the --default-auth\noption is used to specify an authentication plugin but mysqlcheck does not find it. See\nSection 8.2.17, “Pluggable Authentication”.\n\n•   --port=portnum, -P portnum\n\n┌────────────────────┬─────────────────┐\n│Command-Line Format │ --port=portnum │\n├────────────────────┼─────────────────┤\n│Type                │ Numeric         │\n├────────────────────┼─────────────────┤\n│Default Value       │ 3306            │\n└────────────────────┴─────────────────┘\nFor TCP/IP connections, the port number to use.\n\n•   --print-defaults\n\n┌────────────────────┬──────────────────┐\n│Command-Line Format │ --print-defaults │\n└────────────────────┴──────────────────┘\nPrint the program name and all options that it gets from option files.\n\nFor additional information about this and other option-file options, see Section 6.2.2.3,\n“Command-Line Options that Affect Option-File Handling”.\n\n•   --protocol={TCP|SOCKET|PIPE|MEMORY}\n\n┌────────────────────┬───────────────────┐\n│Command-Line Format │ --protocol=type   │\n├────────────────────┼───────────────────┤\n│Type                │ String            │\n├────────────────────┼───────────────────┤\n│Default Value       │ [see text]        │\n├────────────────────┼───────────────────┤\n│Valid Values        │                   │\n│                    │            TCP    │\n│                    │                   │\n│                    │            SOCKET │\n│                    │                   │\n│                    │            PIPE   │\n│                    │                   │\n│                    │            MEMORY │\n└────────────────────┴───────────────────┘\nThe transport protocol to use for connecting to the server. It is useful when the other\nconnection parameters normally result in use of a protocol other than the one you want.\nFor details on the permissible values, see Section 6.2.7, “Connection Transport\nProtocols”.\n\n•   --quick, -q\n\n┌────────────────────┬─────────┐\n│Command-Line Format │ --quick │\n└────────────────────┴─────────┘\nIf you are using this option to check tables, it prevents the check from scanning the\nrows to check for incorrect links. This is the fastest check method.\n\nIf you are using this option to repair tables, it tries to repair only the index tree.\nThis is the fastest repair method.\n\n•   --repair, -r\n\n┌────────────────────┬──────────┐\n│Command-Line Format │ --repair │\n└────────────────────┴──────────┘\nPerform a repair that can fix almost anything except unique keys that are not unique.\n\n•   --server-public-key-path=filename\n\n┌────────────────────┬──────────────────────┐\n│Command-Line Format │ --server-public-key- │\n│                    │ path=filename       │\n├────────────────────┼──────────────────────┤\n│Type                │ File name            │\n└────────────────────┴──────────────────────┘\nThe path name to a file in PEM format containing a client-side copy of the public key\nrequired by the server for RSA key pair-based password exchange. This option applies to\nclients that authenticate with the sha256password or cachingsha2password\nauthentication plugin. This option is ignored for accounts that do not authenticate with\none of those plugins. It is also ignored if RSA-based password exchange is not used, as\nis the case when the client connects to the server using a secure connection.\n\nIf --server-public-key-path=filename is given and specifies a valid public key file, it\ntakes precedence over --get-server-public-key.\n\nFor sha256password, this option applies only if MySQL was built using OpenSSL.\n\nFor information about the sha256password and cachingsha2password plugins, see\nSection 8.4.1.3, “SHA-256 Pluggable Authentication”, and Section 8.4.1.2, “Caching SHA-2\nPluggable Authentication”.\n\n•   --shared-memory-base-name=name\n\n┌────────────────────┬────────────────────────────────┐\n│Command-Line Format │ --shared-memory-base-name=name │\n├────────────────────┼────────────────────────────────┤\n│Platform Specific   │ Windows                        │\n└────────────────────┴────────────────────────────────┘\nOn Windows, the shared-memory name to use for connections made using shared memory to a\nlocal server. The default value is MYSQL. The shared-memory name is case-sensitive.\n\nThis option applies only if the server was started with the sharedmemory system variable\nenabled to support shared-memory connections.\n\n•   --silent, -s\n\n┌────────────────────┬──────────┐\n│Command-Line Format │ --silent │\n└────────────────────┴──────────┘\nSilent mode. Print only error messages.\n\n•   --skip-database=dbname\n\n┌────────────────────┬─────────────────────────┐\n│Command-Line Format │ --skip-database=dbname │\n└────────────────────┴─────────────────────────┘\nDo not include the named database (case-sensitive) in the operations performed by\nmysqlcheck.\n\n•   --socket=path, -S path\n\n┌────────────────────┬────────────────────────────────┐\n│Command-Line Format │ --socket={filename|pipename} │\n├────────────────────┼────────────────────────────────┤\n│Type                │ String                         │\n└────────────────────┴────────────────────────────────┘\nFor connections to localhost, the Unix socket file to use, or, on Windows, the name of\nthe named pipe to use.\n\nOn Windows, this option applies only if the server was started with the namedpipe system\nvariable enabled to support named-pipe connections. In addition, the user making the\nconnection must be a member of the Windows group specified by the\nnamedpipefullaccessgroup system variable.\n\n•   --ssl* Options that begin with --ssl specify whether to connect to the server using\nencryption and indicate where to find SSL keys and certificates. See the section called\n“Command Options for Encrypted Connections”.\n\n•   --ssl-fips-mode={OFF|ON|STRICT}\n\n┌────────────────────┬─────────────────────────────────┐\n│Command-Line Format │ --ssl-fips-mode={OFF|ON|STRICT} │\n├────────────────────┼─────────────────────────────────┤\n│Deprecated          │ 8.0.34                          │\n├────────────────────┼─────────────────────────────────┤\n│Type                │ Enumeration                     │\n├────────────────────┼─────────────────────────────────┤\n│Default Value       │ OFF                             │\n├────────────────────┼─────────────────────────────────┤\n│Valid Values        │                                 │\n│                    │            OFF                  │\n│                    │                                 │\n│                    │            ON                   │\n│                    │                                 │\n│                    │            STRICT               │\n└────────────────────┴─────────────────────────────────┘\nControls whether to enable FIPS mode on the client side. The --ssl-fips-mode option\ndiffers from other --ssl-xxx options in that it is not used to establish encrypted\nconnections, but rather to affect which cryptographic operations to permit. See\nSection 8.8, “FIPS Support”.\n\nThese --ssl-fips-mode values are permitted:\n\n•   OFF: Disable FIPS mode.\n\n•   ON: Enable FIPS mode.\n\n•   STRICT: Enable “strict” FIPS mode.\n\n\nNote\nIf the OpenSSL FIPS Object Module is not available, the only permitted value for\n--ssl-fips-mode is OFF. In this case, setting --ssl-fips-mode to ON or STRICT causes\nthe client to produce a warning at startup and to operate in non-FIPS mode.\nAs of MySQL 8.0.34, this option is deprecated. Expect it to be removed in a future\nversion of MySQL.\n\n•   --tables\n\n┌────────────────────┬──────────┐\n│Command-Line Format │ --tables │\n└────────────────────┴──────────┘\nOverride the --databases or -B option. All name arguments following the option are\nregarded as table names.\n\n•   --tls-ciphersuites=ciphersuitelist\n\n┌────────────────────┬───────────────────────────────┐\n│Command-Line Format │ --tls-                        │\n│                    │ ciphersuites=ciphersuitelist │\n├────────────────────┼───────────────────────────────┤\n│Introduced          │ 8.0.16                        │\n├────────────────────┼───────────────────────────────┤\n│Type                │ String                        │\n└────────────────────┴───────────────────────────────┘\nThe permissible ciphersuites for encrypted connections that use TLSv1.3. The value is a\nlist of one or more colon-separated ciphersuite names. The ciphersuites that can be named\nfor this option depend on the SSL library used to compile MySQL. For details, see\nSection 8.3.2, “Encrypted Connection TLS Protocols and Ciphers”.\n\nThis option was added in MySQL 8.0.16.\n\n•   --tls-version=protocollist\n\n┌─────────────────────────┬──────────────────────────────────────────┐\n│Command-Line Format      │ --tls-version=protocollist              │\n├─────────────────────────┼──────────────────────────────────────────┤\n│Type                     │ String                                   │\n├─────────────────────────┼──────────────────────────────────────────┤\n│Default Value (≥≥ 8.0.16) │                                          │\n│                         │            TLSv1,TLSv1.1,TLSv1.2,TLSv1.3 │\n│                         │            (OpenSSL 1.1.1 or             │\n│                         │            higher)                       │\n│                         │                                          │\n│                         │            TLSv1,TLSv1.1,TLSv1.2         │\n│                         │            (otherwise)                   │\n├─────────────────────────┼──────────────────────────────────────────┤\n│Default Value (≤≤ 8.0.15) │ TLSv1,TLSv1.1,TLSv1.2                    │\n└─────────────────────────┴──────────────────────────────────────────┘\nThe permissible TLS protocols for encrypted connections. The value is a list of one or\nmore comma-separated protocol names. The protocols that can be named for this option\ndepend on the SSL library used to compile MySQL. For details, see Section 8.3.2,\n“Encrypted Connection TLS Protocols and Ciphers”.\n\n•   --use-frm\n\n┌────────────────────┬───────────┐\n│Command-Line Format │ --use-frm │\n└────────────────────┴───────────┘\nFor repair operations on MyISAM tables, get the table structure from the data dictionary\nso that the table can be repaired even if the .MYI header is corrupted.\n\n•   --user=username, -u username\n\n┌────────────────────┬───────────────────┐\n│Command-Line Format │ --user=username, │\n├────────────────────┼───────────────────┤\n│Type                │ String            │\n└────────────────────┴───────────────────┘\nThe user name of the MySQL account to use for connecting to the server.\n\n•   --verbose, -v\n\n┌────────────────────┬───────────┐\n│Command-Line Format │ --verbose │\n└────────────────────┴───────────┘\nVerbose mode. Print information about the various stages of program operation.\n\n•   --version, -V\n\n┌────────────────────┬───────────┐\n│Command-Line Format │ --version │\n└────────────────────┴───────────┘\nDisplay version information and exit.\n\n•   --write-binlog\n\n┌────────────────────┬────────────────┐\n│Command-Line Format │ --write-binlog │\n└────────────────────┴────────────────┘\nThis option is enabled by default, so that ANALYZE TABLE, OPTIMIZE TABLE, and REPAIR\nTABLE statements generated by mysqlcheck are written to the binary log. Use\n--skip-write-binlog to cause NOWRITETOBINLOG to be added to the statements so that\nthey are not logged. Use the --skip-write-binlog when these statements should not be sent\nto replicas or run when using the binary logs for recovery from backup.\n\n•   --zstd-compression-level=level\n\n┌────────────────────┬────────────────────────────┐\n│Command-Line Format │ --zstd-compression-level=# │\n├────────────────────┼────────────────────────────┤\n│Introduced          │ 8.0.18                     │\n├────────────────────┼────────────────────────────┤\n│Type                │ Integer                    │\n└────────────────────┴────────────────────────────┘\nThe compression level to use for connections to the server that use the zstd compression\nalgorithm. The permitted levels are from 1 to 22, with larger values indicating\nincreasing levels of compression. The default zstd compression level is 3. The\ncompression level setting has no effect on connections that do not use zstd compression.\n\nFor more information, see Section 6.2.8, “Connection Compression Control”.\n\nThis option was added in MySQL 8.0.18.\n",
            "subsections": []
        },
        "COPYRIGHT": {
            "content": "Copyright © 1997, 2024, Oracle and/or its affiliates.\n\nThis documentation is free software; you can redistribute it and/or modify it only under the\nterms of the GNU General Public License as published by the Free Software Foundation; version\n2 of the License.\n\nThis documentation is distributed in the hope that it will be useful, but WITHOUT ANY\nWARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR\nPURPOSE. See the GNU General Public License for more details.\n\nYou should have received a copy of the GNU General Public License along with the program; if\nnot, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA\n02110-1301 USA or see http://www.gnu.org/licenses/.\n\n",
            "subsections": []
        },
        "SEE ALSO": {
            "content": "For more information, please refer to the MySQL Reference Manual, which may already be\ninstalled locally and which is also available online at http://dev.mysql.com/doc/.\n",
            "subsections": []
        },
        "AUTHOR": {
            "content": "Oracle Corporation (http://dev.mysql.com/).\n\n\n\nMySQL 8.0                                    12/13/2024                                MYSQLCHECK(1)",
            "subsections": []
        }
    },
    "summary": "mysqlcheck - a table maintenance program",
    "flags": [],
    "examples": [],
    "see_also": []
}