tablespace file, calculates the checksum for each page, compares the calculated checksum to the stored checksum, and reports mismatches, which indicate damaged pages\&. It was originally developed to speed up verifying the integrity of tablespace files after power outages but can also be used after file copies\&. Because checksum mismatches will cause
InnoDB
to deliberately shut down a running server, it can be preferable to use this tool rather than waiting for a server in production usage to encounter the damaged pages\&.
.PP
\fBinnochecksum\fR
cannot be used on tablespace files that the server already has open\&. For such files, you should use
CHECK TABLE
to check tables within the tablespace\&.
.PP
If checksum mismatches are found, you would normally restore the tablespace from backup or start the server and attempt to use
\fBmysqldump\fR
to make a backup of the tables within the tablespace\&.
@ -334,8 +334,18 @@ to display result set metadata\&.
.sp
Use
\fIcharset_name\fR
as the default character set\&. See
Section\ \&9.2, \(lqThe Character Set Used for Data and Sorting\(rq\&.
as the default character set for the client and connection\&.
.sp
A common issue that can occur when the operating system uses
utf8
or another multi\-byte character set is that output from the
\fBmysql\fR
client is formatted incorrectly, due to the fact that the MySQL client uses the
latin1
character set by default\&. You can usually fix such issues by using this option to force the client to use the system character set instead\&.
.sp
See
Section\ \&9.2, \(lqThe Character Set Used for Data and Sorting\(rq, for more information\&.
.RE
.sp
.RS 4
@ -648,7 +658,7 @@ PAGER
environment variable\&. Valid pagers are
\fBless\fR,
\fBmore\fR,
\fBcat [> filename]\fR, and so forth\&. This option works only on Unix\&. It does not work in batch mode\&. To disable paging, use
\fBcat [> filename]\fR, and so forth\&. This option works only on Unix and only in interactive mode\&. To disable paging, use
\fB\-\-skip\-pager\fR\&.
the section called \(lqMYSQL COMMANDS\(rq, discusses output paging further\&.
.RE
@ -1026,7 +1036,7 @@ Display output in table format\&. This is the default for interactive use, but c
.\" tee option: mysql
\fB\-\-tee=\fR\fB\fIfile_name\fR\fR
.sp
Append a copy of output to the given file\&. This option does not work in batch mode\&.
Append a copy of output to the given file\&. This option works only in interactive mode\&.
the section called \(lqMYSQL COMMANDS\(rq, discusses tee files further\&.
.RE
.sp
@ -1523,7 +1533,7 @@ is set to something other than the default of
\(lq;\(rq, instances of that character are sent to the server without interpretation\&. However, the server itself still interprets
\(lq;\(rq
as a statement delimiter and processes statements accordingly\&. This behavior on the server side comes into play for multiple\-statement execution (see
Section\ \&21.10.12, \(lqC API Support for Multiple Statement Execution\(rq), and for parsing the body of stored procedures and functions, triggers, and events (see
Section\ \&21.9.12, \(lqC API Support for Multiple Statement Execution\(rq), and for parsing the body of stored procedures and functions, triggers, and events (see
environment variable and sets the pager to that\&.
environment variable and sets the pager to that\&. Pager functionality works only in interactive mode\&.
.sp
Output paging can be enabled interactively with the
\fBpager\fR
@ -1853,7 +1863,7 @@ By using the
option when you invoke
\fBmysql\fR, you can log statements and their output\&. All the data displayed on the screen is appended into a given file\&. This can be very useful for debugging purposes also\&.
\fBmysql\fR
flushes results to the file after each statement, just before it prints its next prompt\&.
flushes results to the file after each statement, just before it prints its next prompt\&. Tee functionality works only in interactive mode\&.
.sp
You can enable this feature interactively with the
In this example, note that the backslashes are doubled\&. If you set the prompt using the
prompt
option in an option file, it is advisable to double the backslashes when using the special prompt options\&. There is some overlap in the set of allowable prompt options and the set of special escape sequences that are recognized in option files\&. (These sequences are listed in
option in an option file, it is advisable to double the backslashes when using the special prompt options\&. There is some overlap in the set of allowable prompt options and the set of special escape sequences that are recognized in option files\&. (The rules for escape sequences in option files are listed in
Section\ \&4.2.3.3, \(lqUsing Option Files\(rq\&.) The overlap may cause you problems if you use single backslashes\&. For example,
\es
is interpreted as a space rather than as the current seconds value\&. The following example shows how to define a prompt within an option file to include the current time in
@ -2586,6 +2596,12 @@ SELECT \'<info_to_display>\' AS \' \';
The statement shown outputs
<info_to_display>\&.
.PP
You can also invoke
\fBmysql\fR
with the
\fB\-\-verbose\fR
option, which causes each statement to be displayed before the result that it produces\&.
.PP
As of MySQL 5\&.1\&.23,
\fBmysql\fR
ignores Unicode byte order mark (BOM) characters at the beginning of input files\&. Previously, it read them and sent them to the server, resulting in a syntax error\&. Presence of a BOM does not cause
@ -2785,7 +2801,7 @@ client with the
option\&.
.PP
For more information about auto\-reconnect and its effect on state information when a reconnection occurs, see
Some upgrade incompatibilities may require special handling before you upgrade your MySQL installation and run
\fBmysql_upgrade\fR\&. See
Section\ \&2.12.1, \(lqUpgrading MySQL\(rq, for instructions on determining whether any such incompatibilities apply to your installation and how to handle them\&.
Section\ \&2.4.1, \(lqUpgrading MySQL\(rq, for instructions on determining whether any such incompatibilities apply to your installation and how to handle them\&.
.sp .5v
.RE
.PP
@ -189,7 +189,7 @@ If you install MySQL from RPM packages on Linux, you must install the server and
\fBmysql_upgrade\fR
is included in the server RPM but requires the client RPM because the latter includes
\fBmysqlcheck\fR\&. (See
Section\ \&2.4, \(lqInstalling MySQL from RPM Packages on Linux\(rq\&.)
Section\ \&2.6.1, \(lqInstalling MySQL from RPM Packages on Linux\(rq\&.)
.PP
In MySQL 5\&.1\&.7,
\fBmysql_upgrade \fR
@ -352,6 +352,26 @@ root\&.
.sp
Verbose mode\&. Print more information about what the program does\&.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
.\" mysql_upgrade: write-binlog option
.\" write-binlog option: mysql_upgrade
\fB\-\-write\-binlog\fR
.sp
Cause binary logging to be enabled while
\fBmysql_upgrade\fR
runs\&. This is the default behavior; to disable binary logging during the upgrade, use the inverse of this option (that is, start the program with
client performs table maintenance: It checks, repairs, optimizes, or analyzes tables\&.
.PP
Each table is locked and therefore unavailable to other sessions while it is being processed\&. Table maintenance operations can be time\-consuming, particularly for large tables\&. If you use the
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\ \&12.4.5, \(lqLOCK TABLES and UNLOCK TABLES Syntax\(rq, for more information about
READ
and
WRITE
locks)\&. Table maintenance operations can be time\-consuming, particularly for large tables\&. If you use the
\fB\-\-databases\fR
or
\fB\-\-all\-databases\fR
@ -94,7 +101,7 @@ note : The storage engine for the table doesn\'t support check
If
\fBmysqlcheck\fR
is unable to repair a table, see
Section\ \&2.12.4, \(lqRebuilding or Repairing Tables or Indexes\(rq
Section\ \&2.4.4, \(lqRebuilding or Repairing Tables or Indexes\(rq
for manual table repair strategies\&. This will be the case, for example, for
@ -51,7 +51,7 @@ to specify which servers you want to start, stop, or obtain a status report for\
[mysqld]
group used for starting
\fBmysqld\fR\&. (See, for example,
Section\ \&2.11.2.2, \(lqStarting and Stopping MySQL Automatically\(rq\&.) However, when using multiple servers, it is necessary that each one use its own value for options such as the Unix socket file and TCP/IP port number\&. For more information on which options must be unique per server in a multiple\-server environment, see
Section\ \&2.13.1.2, \(lqStarting and Stopping MySQL Automatically\(rq\&.) However, when using multiple servers, it is necessary that each one use its own value for options such as the Unix socket file and TCP/IP port number\&. For more information on which options must be unique per server in a multiple\-server environment, see
Section\ \&5.6, \(lqRunning Multiple MySQL Servers on the Same Machine\(rq\&.
.PP
To invoke
@ -183,12 +183,6 @@ Otherwise, option files in the standard list of locations are read, including an
option, if one is given\&. (If the option is given multiple times, the last value is used\&.)
.RE
.PP
Option files read are searched for
[mysqld_multi]
and
[mysqld\fIN\fR]
option groups\&.
.PP
Before MySQL 5\&.1\&.18, the preceding options are not recognized\&. Files in the standard locations are read, and any file named by the
\fB\-\-config\-file=\fR\fB\fIfile_name\fR\fR
option, if one is given\&. A file named by
@ -199,6 +193,39 @@ option groups, not the
[mysqld_multi]
group\&.
.PP
Option files read are searched for
[mysqld_multi]
and
[mysqld\fIN\fR]
option groups\&. The
[mysqld_multi]
group can be used for options to
\fBmysqld_multi\fR
itself\&.
[mysqld\fIN\fR]
groups can be used for options passed to specific
\fBmysqld\fR
instances\&.
.PP
As of MySQL 5\&.1\&.35, the
[mysqld]
or
[mysqld_safe]
groups can be used for common options read by all instances of
\fBmysqld\fR
or
\fBmysqld_safe\fR\&. You can specify a
\fB\-\-defaults\-file=\fR\fB\fIfile_name\fR\fR
option to use a different configuration file for that instance, in which case the
[mysqld]
or
[mysqld_safe]
groups from that file will be used for that instance\&. Before MySQL 5\&.1\&.35, some versions of
\fBmysqld_multi\fR
pass the
\fB\-\-no\-defaults\fR
options to instances, so these techniques are inapplicable\&.
This option has no effect for output data files produced by using the
Prior to MySQL 5\&.1\&.38, this option has no effect for output data files produced by using the
\fB\-\-tab\fR
option\&. See the description for that option\&.
.RE
@ -1232,7 +1232,8 @@ statement for the table\&.
\fB\-\-no\-set\-names\fR
.sp
This option is deprecated\&. Use
\fB\-\-skip\-set\-charset\fR\&. instead\&.
\fB\-\-skip\-set\-charset\fR
instead\&.
.RE
.sp
.RS 4
@ -1657,11 +1658,11 @@ and
\fB\-\-lines\-terminated\-by\fR
options\&.
.sp
Column values are dumped using the
binary
character set and the
As of MySQL 5\&.1\&.38, column values are written converted to the character set specified by the
\fB\-\-default\-character\-set\fR
option is ignored\&. In effect, there is no character set conversion\&. If a table contains columns in several character sets, the output data file will as well and you may not be able to reload the file correctly\&.
option\&. Prior to 5\&.1\&.38 or if no such option is present, values are dumped using the
binary
character set\&. In effect, there is no character set conversion\&. If a table contains columns in several character sets, the output data file will as well and you may not be able to reload the file correctly\&.
.if n \{\
.sp
.\}
@ -2110,7 +2111,7 @@ InnoDB
storage engine\&.
.PP
For more information on making backups, see
Section\ \&6.1, \(lqDatabase Backups\(rq, and
Section\ \&6.1, \(lqDatabase Backup Methods\(rq, and
Section\ \&6.2, \(lqExample Backup and Recovery Strategy\(rq\&.
@ -41,8 +41,9 @@ processes cooperate in handling data\&. These processes can execute on the same
.\" command options (MySQL Cluster): ndbd
.\" MySQL Cluster: ndbd process
.PP
The following list describes command options specific to the MySQL Cluster data node program
\fBndbd\fR\&.
The following table includes command options specific to the MySQL Cluster data node program
\fBndbd\fR\&. Additional descriptions follow the table\&. For options common to all MySQL Cluster programs, see
Section\ \&17.4.2, \(lqOptions Common to MySQL Cluster Programs\(rq\&.
.if n \{\
.sp
.\}
@ -68,7 +69,7 @@ wherever the latter occurs in this section\&.
For options common to all
NDBCLUSTER
programs, see
Section\ \&17.6.2, \(lqOptions Common to MySQL Cluster Programs\(rq\&.
Section\ \&17.4.2, \(lqOptions Common to MySQL Cluster Programs\(rq\&.
.sp
.RS 4
.ie n \{\
@ -81,9 +82,11 @@ Section\ \&17.6.2, \(lqOptions Common to MySQL Cluster Programs\(rq\&.
\fB\-\-bind\-address\fR
.TS
allbox tab(:);
l l
l l
l l.
l l s
l l s
l l s
^ l l
^ l l.
T{
\fBVersion Introduced\fR
T}:T{
@ -95,28 +98,16 @@ T}:T{
\-\-bind\-address=name
T}
T{
\fBPermitted Values \fR
\ \&
T}:T{
[\fInested\ table\fR]*
\fBPermitted Values \fR
T}
.TE
.sp 1
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
.B *[nested\ table]
.TS
allbox tab(:);
l l
l l.
T{
:T{
\fBType\fR
T}:T{
string
T}
T{
:T{
\fBDefault\fR
T}:T{
T}
@ -141,36 +132,26 @@ This option was added in MySQL 5\&.1\&.12\&.
\fB\-d\fR
.TS
allbox tab(:);
l l
l l.
l l s
l l s
^ l l
^ l l.
T{
\fBCommand Line Format\fR
T}:T{
\-\-daemon
T}
T{
\fBPermitted Values \fR
\ \&
T}:T{
[\fInested\ table\fR]*
\fBPermitted Values \fR
T}
.TE
.sp 1
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
.B *[nested\ table]
.TS
allbox tab(:);
l l
l l.
T{
:T{
\fBType\fR
T}:T{
boolean
T}
T{
:T{
\fBDefault\fR
T}:T{
TRUE
@ -182,6 +163,12 @@ Instructs
to execute as a daemon process\&. This is the default behavior\&.
\fB\-\-nodaemon\fR
can be used to prevent the process from running as a daemon\&.
.sp
This option has no effect when running
\fBndbd\fR
or
\fBndbmtd\fR
on Windows platforms\&.
.RE
.sp
.RS 4
@ -197,36 +184,26 @@ can be used to prevent the process from running as a daemon\&.
\fB\-\-initial\fR
.TS
allbox tab(:);
l l
l l.
l l s
l l s
^ l l
^ l l.
T{
\fBCommand Line Format\fR
T}:T{
\-\-initial
T}
T{
\fBPermitted Values \fR
\ \&
T}:T{
[\fInested\ table\fR]*
\fBPermitted Values \fR
T}
.TE
.sp 1
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
.B *[nested\ table]
.TS
allbox tab(:);
l l
l l.
T{
:T{
\fBType\fR
T}:T{
boolean
T}
T{
:T{
\fBDefault\fR
T}:T{
FALSE
@ -321,9 +298,11 @@ Backup files that have already been created by the affected node
.IP \(bu 2.3
.\}
MySQL Cluster Disk Data files (see
Section\ \&17.10, \(lqMySQL Cluster Disk Data Tables\(rq)\&.
Section\ \&17.5.9, \(lqMySQL Cluster Disk Data Tables\(rq)\&.
.RE
.RS 4
.sp
This option also has no effect on recovery of data by a data node that is just starting (or restarting) from data nodes that are already running\&. This recovery of data occurs automatically, and requires no user intervention in a MySQL Cluster that is running normally\&.
.sp .5v
.RE
It is permissible to use this option when starting the cluster for the very first time (that is, before any data node files have been created); however, it is
@ -344,9 +323,11 @@ necessary to do so\&.
\fB\-\-initial\-start\fR
.TS
allbox tab(:);
l l
l l
l l.
l l s
l l s
l l s
^ l l
^ l l.
T{
\fBVersion Introduced\fR
T}:T{
@ -358,28 +339,16 @@ T}:T{
\-\-initial\-start
T}
T{
\fBPermitted Values \fR
\ \&
T}:T{
[\fInested\ table\fR]*
\fBPermitted Values \fR
T}
.TE
.sp 1
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
.B *[nested\ table]
.TS
allbox tab(:);
l l
l l.
T{
:T{
\fBType\fR
T}:T{
boolean
T}
T{
:T{
\fBDefault\fR
T}:T{
FALSE
@ -435,9 +404,11 @@ Prior to MySQL 5\&.1\&.19, it was not possible to perform DDL operations involvi
@ -508,36 +467,26 @@ This option was added in MySQL 5\&.1\&.9\&.
\fB\-\-nodaemon\fR
.TS
allbox tab(:);
l l
l l.
l l s
l l s
^ l l
^ l l.
T{
\fBCommand Line Format\fR
T}:T{
\-\-nodaemon
T}
T{
\fBPermitted Values \fR
\ \&
T}:T{
[\fInested\ table\fR]*
\fBPermitted Values \fR
T}
.TE
.sp 1
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
.B *[nested\ table]
.TS
allbox tab(:);
l l
l l.
T{
:T{
\fBType\fR
T}:T{
boolean
T}
T{
:T{
\fBDefault\fR
T}:T{
FALSE
@ -549,6 +498,12 @@ Instructs
not to start as a daemon process\&. This is useful when
\fBndbd\fR
is being debugged and you want output to be redirected to the screen\&.
.sp
As of MySQL Cluster NDB 7\&.0\&.8, the default behavior for
\fBndbd\fR
and
\fBndbmtd\fR
on Windows is to run in the foreground, making this option unnecessary on Windows platforms\&. (\m[blue]\fBBug#45588\fR\m[]\&\s-2\u[2]\d\s+2)
.RE
.sp
.RS 4
@ -567,36 +522,26 @@ is being debugged and you want output to be redirected to the screen\&.
\fB\-n\fR
.TS
allbox tab(:);
l l
l l.
l l s
l l s
^ l l
^ l l.
T{
\fBCommand Line Format\fR
T}:T{
\-\-nostart
T}
T{
\fBPermitted Values \fR
\ \&
T}:T{
[\fInested\ table\fR]*
\fBPermitted Values \fR
T}
.TE
.sp 1
.sp
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
.B *[nested\ table]
.TS
allbox tab(:);
l l
l l.
T{
:T{
\fBType\fR
T}:T{
boolean
T}
T{
:T{
\fBDefault\fR
T}:T{
FALSE
@ -610,7 +555,7 @@ not to start automatically\&. When this option is used,
connects to the management server, obtains configuration data from it, and initializes communication objects\&. However, it does not actually start the execution engine until specifically requested to do so by the management server\&. This can be accomplished by issuing the proper
START
command in the management client (see
Section\ \&17.7.2, \(lqCommands in the MySQL Cluster Management Client\(rq)\&.
Section\ \&17.5.2, \(lqCommands in the MySQL Cluster Management Client\(rq)\&.
Section\ \&17.3.4.3, \(lqThe MySQL Cluster Connectstring\(rq, for additional information about this issue\&.
Section\ \&17.3.2.3, \(lqThe MySQL Cluster Connectstring\(rq, for additional information about this issue\&.
\fBndbd\fR(8), describes other options for
\fBndbd\fR\&.
.PP
@ -810,7 +755,7 @@ process can consume up to 2 CPUs if permitted to do so\&.
For a machine with many CPUs it is possible to use several
\fBndbd\fR
processes which belong to different node groups; however, such a configuration is still considered experimental and is not supported for MySQL 5\&.1 in a production setting\&. See
Section\ \&17.12, \(lqKnown Limitations of MySQL Cluster\(rq\&.
Section\ \&17.1.5, \(lqKnown Limitations of MySQL Cluster\(rq\&.
@ -49,8 +49,8 @@ Command\-line options and configuration parameters used with
\fBndbd\fR
also apply to
\fBndbmtd\fR\&. For more information about these options and parameters, see
Section\ \&17.6.3.2, \(lqProgram Options for ndbd and ndbmtd\(rq, and
Section\ \&17.3.4.6, \(lqDefining MySQL Cluster Data Nodes\(rq, respectively\&.
\fBndbd\fR(8), and
Section\ \&17.3.2.6, \(lqDefining MySQL Cluster Data Nodes\(rq, respectively\&.
.PP
\fBndbmtd\fR
is also file system\-compatible with
@ -69,25 +69,13 @@ simply by stopping the node and then starting
\fBndbd\fR
in place of the multi\-threaded binary\&. It is not necessary when switching between the two to start the data node binary using
\fB\-\-initial\fR\&.
.if n \{\
.sp
.\}
.RS 4
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
.ps +1
\fBImportant\fR
.ps -1
.br
.PP
We do not currently recommend using
Prior to MySQL Cluster NDB 7\&.0\&.6, there were known issues when using
\fBndbmtd\fR
with MySQL Cluster Disk Data tables in production, due to known issues which we are working to fix in a future MySQL Cluster release\&. (\m[blue]\fBBug#41915\fR\m[]\&\s-2\u[1]\d\s+2,
with MySQL Cluster Disk Data tables\&. If you wish to use multi\-threaded data nodes with disk\-based
NDB
tables, you should insure that you are running MySQL Cluster NDB 7\&.0\&.6 or later\&. (\m[blue]\fBBug#41915\fR\m[]\&\s-2\u[1]\d\s+2,
\m[blue]\fBBug#44915\fR\m[]\&\s-2\u[2]\d\s+2)
.sp .5v
.RE
.PP
Using
\fBndbmtd\fR
@ -129,6 +117,8 @@ failures\&.
.RE
.PP
These differences are discussed in more detail in the next few paragraphs\&.
.\" execution threads (MySQL Cluster)
.\" MySQL Cluster: execution threads
.\" ndbmtd: MaxNoOfExecutionThreads
.\" MaxNoOfExecutionThreads: ndbmtd
.\" ndbmtd: trace files
@ -148,7 +138,7 @@ file, it is exclusive to
and does not apply to
\fBndbd\fR\&.
.PP
This parameter takes an integer value from 2 to 8 inclusive\&. Generally, you should set this to the number of CPU cores on the data node host, as shown in the following table:
This parameter takes an integer value from 2 to 8 inclusive\&. Generally, you should set this parameter equal to the number of CPU cores on the data node host, as shown in the following table:
unknown
16 years ago