mysql 更新方法

Performing an In-place Upgrade      

This section describes how to perform an in-place upgrade. Review Before you Begin before proceeding.

Note

If you upgrade an installation originally produced by installing multiple RPM packages, upgrade all the packages, not just some. For example, if you previously installed the server and client RPMs, do not upgrade just the server RPM.

To perform an in-place upgrade:

1. Review the changes described in Section 2.11.1.1, “Changes Affecting Upgrades to MySQL 5.7” for steps to be performed before upgrading.
2. Configure MySQL to perform a slow shutdown by setting 

   innodb_fast_shutdown

    to  . For example:

   shell>          bin/mysql -u root -p          password                 --execute="set global innodb_fast_shutdown=0"           

   With a slow shutdown, 

   InnoDB

    performs a full purge and change buffer merge before shutting down, which ensures that data files are fully prepared in case of file format differences between releases.
3. Shut down the old MySQL server. For example:

   shell>          bin/mysqladmin -u root -p          password                 shutdown           

4. Upgrade the MySQL binaries or packages in place, replacing the old binaries or packages with the new ones.

   For supported Linux distributions, the preferred method for replacing the MySQL packages is to use the MySQL software repositories; see Section 2.11.1.2, “Upgrading MySQL with the MySQL Yum Repository”, Section 2.11.1.3, “Upgrading MySQL with the MySQL APT Repository”, or Upgrading MySQL with the MySQL SLES Repository for instructions.

5. Start the MySQL 5.7 server, using the existing data directory. For example:

   shell>          bin/mysqld_safe --user=mysql --datadir=         /path/to/existing-datadir                

6. Run mysql_upgrade. For example:

   shell>          bin/mysql_upgrade -u root -p          password                

   mysql_upgrade examines all tables in all databases for incompatibilities with the current version of MySQL. mysql_upgrade also upgrades the system tables so that you can take advantage of new privileges or capabilities.

   mysql_upgrade should not be used when the server is running with 

   --gtid-mode=ON

   . See GTID mode and mysql_upgrade for more information.

   mysql_upgrade does not upgrade the contents of the help tables. For upgrade instructions, see Section 6.1.9, “Server-Side Help”.

Performing a Logical Upgrade      

This section describes how to perform a logical upgrade. Review Before you Begin before proceeding.

To perform a logical upgrade:

2. Export your existing data from the previous MySQL version:

   shell>          mysqldump --add-drop-table --routines --events                
       ->          --all-databases --force > data-for-upgrade.sql           

   Use the 

   --routines

    and 

   --events

    options with mysqldump (as shown above) if your databases include stored programs. The 

   --all-databases

    option includes all databases in the dump, including the 

   mysql

    database that holds the system tables.

   Important

   If you have tables that contain generated columns, use the mysqldump utility provided with MySQL 5.7.9 or higher to create your dump files. The mysqldump utility provided in earlier releases uses incorrect syntax for generated column definitions (Bug #20769542). You can use the 

   INFORMATION_SCHEMA.COLUMNS

    table to identify tables with generated columns.

3. shell>          bin/mysqladmin -u root -p          password                 shutdown           

4. Install MySQL 5.7. For installation instructions, see Chapter 2, Installing and Upgrading MySQL.
5. Initialize a new data directory:

   shell>          mysqld --initialize --datadir=         /path/to/5.7-datadir                

   Copy the temporary 

   'root'@'localhost'

    password printed to your screen or written to your error log for later use.
6. Start the MySQL 5.7 server, using the new data directory. For example:

   shell>          bin/mysqld_safe --user=mysql --datadir=         /path/to/5.7-datadir                

7. Reset the 

   root

    password:

   shell>          mysql -u root -p                
   Enter password:          ****                  <- enter temporary root password
   mysql>          ALTER USER USER() IDENTIFIED BY '         your new password                ';           

8. Load the previously created dump file into the new MySQL server. For example:

   shell>          bin/mysql -u root -p          password                 --execute="source data-for-upgrade.sql" --force           

9. shell>          bin/mysql_upgrade -u root -p          password                

   --gtid-mode=ON

10. innodb_fast_shutdown

    shell>          bin/mysql -u root -p          password                 --execute="set global innodb_fast_shutdown=0"           

11. Shut down and restart the MySQL server to ensure a clean shutdown and startup. For example:

    shell>          bin/mysqladmin -u root -p          password                 shutdown                
    shell>          bin/mysqld_safe --user=mysql --datadir=         /path/to/5.7-datadir                

Upgrade Troubleshooting

• If problems occur, such as that the new mysqld server does not start or that you cannot connect without a password, verify that you do not have an old 

  my.cnf

   file from your previous installation. You can check this with the 

  --print-defaults

   option (for example, mysqld --print-defaults). If this command displays anything other than the program name, you have an active 

  my.cnf

   file that affects server or client operation.
• If, after an upgrade, you experience problems with compiled client programs, such as 

  Commands out of sync

   or unexpected core dumps, you probably have used old header or library files when compiling your programs. In this case, check the date for your 

  mysql.h

   file and

  libmysqlclient.a

   library to verify that they are from the new MySQL distribution. If not, recompile your programs with the new headers and libraries. Recompilation might also be necessary for programs compiled against the shared client library if the library major version number has changed (for example from 

  libmysqlclient.so.15

  libmysqlclient.so.16

  .
• If you have created a user-defined function (UDF) with a given name and upgrade MySQL to a version that implements a new built-in function with the same name, the UDF becomes inaccessible. To correct this, use 

  DROP FUNCTION

   to drop the UDF, and then use 

  CREATE FUNCTION

   to re-create the UDF with a different nonconflicting name. The same is true if the new version of MySQL implements a built-in function with the same name as an existing stored function. See Section 10.2.4, “Function Name Parsing and Resolution”, for the rules describing how the server interprets references to different kinds of functions.