mysql_upgrade man page on Peanut

Man page or keyword search:  
man Server   7435 pages
apropos Keyword Search (all sections)
Output format
Peanut logo
[printable version]

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 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.

       To check and repair tables and to upgrade the system tables,
       mysql_upgrade executes the following commands:

	  mysqlcheck --check-upgrade --all-databases --auto-repair
	  mysql_fix_privilege_tables

       mysql_upgrade supersedes the older mysql_fix_privilege_tables script.
       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. On systems older
       than those supporting mysql_upgrade, you can execute the mysqlcheck
       command manually, and then upgrade your system tables as described in
       mysql_fix_privilege_tables(1).

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

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

	  shell> mysql_upgrade [options]

       mysql_upgrade reads options from the command line and from the
       [mysql_upgrade] group in option files. It supports the following
       options:

       ·  --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

	  Force execution of mysqlcheck even if mysql_upgrade has already been
	  executed for the current version of MySQL. (In other words, this
	  option causes the mysql_upgrade.info file to be ignored.)

       ·  --user=user_name, -u user_name

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

       ·  --verbose

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

       Other options are passed to mysqlcheck and to
       mysql_fix_privilege_tables. For example, it might be necessary to
       specify the --password[=password] option.

COPYRIGHT
       Copyright 1997-2006 MySQL AB

       This documentation is NOT distributed under a GPL license. Use of this
       documentation is subject to the following terms: You may create a
       printed copy of this documentation solely for your own personal use.
       Conversion to other formats is allowed as long as the actual content is
       not altered or edited in any way. You shall not publish or distribute
       this documentation in any form or on any media, except if you
       distribute the documentation in a manner similar to how MySQL
       disseminates it (that is, electronically for download on a Web site
       with the software) or on a CD-ROM or similar medium, provided however
       that the documentation is disseminated together with the software on
       the same medium. Any other use, such as any dissemination of printed
       copies or use of this documentation, in whole or in part, in another
       publication, requires the prior written consent from an authorized
       representative of MySQL AB. MySQL AB reserves any and all rights to
       this documentation not expressly granted above.

       Please email <docs@mysql.com> for more information.

SEE ALSO
       msql2mysql(1), my_print_defaults(1), myisam_ftdump(1), myisamchk(1),
       myisamlog(1), myisampack(1), mysql(1), mysql.server(1),
       mysql_config(1), mysql_explain_log(1), mysql_fix_privilege_tables(1),
       mysql_tzinfo_to_sql(1), mysql_zap(1), mysqlaccess(1), mysqladmin(1),
       mysqlbinlog(1), mysqlcheck(1), mysqld(8), mysqld_multi(1),
       mysqld_safe(1), mysqldump(1), mysqlhotcopy(1), mysqlimport(1),
       mysqlmanager(8), mysqlshow(1), perror(1), replace(1), safe_mysqld(1)

       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
       MySQL AB (http://www.mysql.com/).  This software comes with no
       warranty.

MySQL 5.0			  01/09/2007		      MYSQL_UPGRADE(1)
[top]

List of man pages available for Peanut

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net