|
|
| Applications |
| Mailing Lists |
| Miscellaneous |
| Operating Systems |
| Programming |
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.
Caution
Some upgrade incompatibilities may require special handling before you upgrade your MySQL installation and run mysql_upgrade. See Section 2.11, “Upgrading MySQLâ€, for instructions on determining whether any such incompatibilies apply to your installation and how to handle them.
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.1.7, mysql_upgrade was added as a shell script and worked only for Unix systems. As of MySQL 5.1.10, 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 Section 4.4.4, “mysql_fix_privilege_tables — Upgrade MySQL System Tablesâ€.
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.4, “Installing MySQL from RPM Packages on Linuxâ€.)
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â€).
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 it uses any changes that were made to the system tables.
mysql_upgrade reads options from the command
line and from the [mysql_upgrade] group in
option files. It supports the following options:
Display a short help message and exit.
The path to the MySQL installation directory.
The path to the data directory.
Print some debugging information when the program exits. This option was added in MySQL 5.1.21.
Print debugging information and memory and CPU usage statistics when the program exits. This option was added in MySQL 5.1.21.
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_infofile to be ignored.)The pathname of the directory to use for creating temporary files. This option was added in MySQL 5.1.25.
--user=,user_name-uuser_nameThe MySQL username to use when connecting to the server. The default username is
root.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[=
option.
password]
|
Contact Us Legal Notices Order Services Online Pantek Home Privacy Policy IT news Site Map Pantek Library |
User Comments
Be careful when you have multiple instances of mysqld running on the same box.
mysql_upgrade reads the sections [mysql_upgrade] and [client] for default values. The values required for an update, notably datadir and friends, are in [mysqld], though. Thus, it will touch the default datadir in /var/lib/mysql as it will not see your special datadir.
You cannot copy my.cnf and rename [mysqld] to [mysql_upgrade], because mysql_upgrade chokes on all the mysqld options. Instead filter the options you need like this:
( echo '[mysql_upgrade]';
$PATHTO/my_print_defaults
--defaults-file=$PATHTO/my.cnf mysqld |
egrep '(datadir|basedir|user|password|socket)' |
sed -e 's/^--//';
) >> $PATHTO/my.cnf
Now mysqld_upgrade will find the information necessary to run properly. Check with
mysql_upgrade --defaults-file=$PATHTO/my.cnf --print-defaults
then run with
mysql_upgrade --defaults-file=$PATHTO/my.cnf -v
Add your own comment.