This manual page is for Mac OS X Server version 10.6

If you are running Mac OS X (client), this command is not available.

If you are running a different version of Mac OS X Server, view the documentation locally:

  • In Xcode

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • For more information about the manual page format, see the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Reference Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.



MYSQL_UPGRADE(1)                            MySQL Database System                           MYSQL_UPGRADE(1)



NAME
       mysql_upgrade - check tables for MySQL upgrade

SYNOPSIS
       mysql_upgrade [options]

DESCRIPTION
       mysql_upgrade should be executed each time you upgrade MySQL. It supersedes the older
       mysql_fix_privilege_tables script, which should no longer be used.

       mysql_upgrade checks all tables in all databases for incompatibilities with the current version of
       MySQL Server. If a table is found to have a possible incompatibility, it is checked. If any problems
       are found, the table is repaired.  mysql_upgrade also upgrades the system tables so that you can take
       advantage of new privileges or capabilities that might have been added.

       All checked and repaired tables are marked with the current MySQL version number. This ensures that
       next time you run mysql_upgrade with the same version of the server, it can tell whether there is any
       need to check or repair the table again.

       mysql_upgrade also saves the MySQL version number in a file named mysql_upgrade_info in the data
       directory. This is used to quickly check if all tables have been checked for this release so that
       table-checking can be skipped. To ignore this file, use the --force option.

       Caution
       Some upgrade incompatibilities may require special handling before you upgrade your MySQL
       installation and run mysql_upgrade. See Section 2.18.1, "Upgrading MySQL", for instructions on
       determining whether any such incompatibilities apply to your installation and how to handle them.

       mysql_upgrade executes the following commands to check and repair tables and to upgrade the system
       tables.  fix_priv_tables represents a script generated interally by mysql_upgrade that contains SQL
       statements to upgrade the tables in the mysql database:

          mysqlcheck --check-upgrade --all-databases --auto-repair
          mysql < fix_priv_tables

       For details about what is checked, see the description of the FOR UPGRADE option of the CHECK TABLE
       statement (see Section 12.5.2.3, "CHECK TABLE Syntax").

       In MySQL 5.0.19, mysql_upgrade was added as a shell script and worked only for Unix systems. As of
       MySQL 5.0.25, mysql_upgrade is an executable binary and is available on all systems.

       If you install MySQL from RPM packages on Linux, you must install the server and client RPMs.
       mysql_upgrade is included in the server RPM but requires the client RPM because the latter includes
       mysqlcheck. (See Section 2.10, "Installing MySQL from RPM Packages on Linux".)

       To use mysql_upgrade, make sure that the server is running, and then invoke it like this:

          shell> mysql_upgrade [options]

       After running mysql_upgrade, stop the server and restart it so that any changes made to the system
       tables take effect.

       mysql_upgrade supports the options in the following list. It also reads option files (the
       [mysql_upgrade] and [client] groups) and supports the options for processing them described at
       Section 4.2.3.2.1, "Command-Line Options that Affect Option-File Handling". Other options are passed
       to mysqlcheck. For example, it might be necessary to specify the --password[=password] option.

         --help

          Display a short help message and exit.

         --basedir=path

          The path to the MySQL installation directory.

         --datadir=path

          The path to the data directory.

         --force

          Ignore the mysql_upgrade_info file and force execution of mysqlcheck even if mysql_upgrade has
          already been executed for the current version of MySQL.

         --tmpdir=path, -t path

          The path name of the directory to use for creating temporary files. This option was added in MySQL
          5.0.62.

         --user=user_name, -u user_name

          The MySQL user name to use when connecting to the server. The default user name is root.

         --verbose

          Verbose mode. Print more information about what the program does.

COPYRIGHT
       Copyright 2007-2008 MySQL AB, 2009 Sun Microsystems, Inc.

       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 available online at http://dev.mysql.com/doc/.

AUTHOR
       Sun Microsystems, Inc. (http://www.mysql.com/).



MySQL 5.0                                        05/07/2009                                 MYSQL_UPGRADE(1)

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.