2.11.1.5 Upgrading MySQL Binary or Package-based Installations on Unix/Linux

Review the information in Section 2.11.1.1, “Before You Begin”.

Ensure the upgrade readiness of your installation by completing the preliminary checks in Section 2.11.1.4, “Preparing Your Installation for Upgrade”.

If you use XA transactions with InnoDB, run XA RECOVER before upgrading to check for uncommitted XA transactions. If results are returned, either commit or rollback the XA transactions by issuing an XA COMMIT or XA ROLLBACK statement.

If there are encrypted InnoDB tablespaces, rotate the keyring master key by executing this statement:

If you normally run your MySQL server configured with innodb_fast_shutdown set to 2 (cold shutdown), configure it to perform a fast or slow shutdown by executing either of these statements:

With a fast or slow shutdown, InnoDB leaves its undo logs and data files in a state that can be dealt with in case of file format differences between releases.

Shut down the old MySQL server. For example:

mysqladmin -u root -p shutdown

Upgrade the MySQL binaries or packages. If upgrading a binary installation, unpack the new MySQL binary distribution package. See Obtain and Unpack the Distribution. For package-based installations, install the new packages.

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

mysqld_safe --user=mysql --datadir=/path/to/existing-datadir

If there are encrypted InnoDB tablespaces, use the --early-plugin-load option to load the keyring plugin.

When you start the MySQL 8.0 server, it automatically detects whether data dictionary tables are present. If not, the server creates them in the data directory, populates them with metadata, and then proceeds with its normal startup sequence. During this process, the server upgrades metadata for all database objects, including databases, tablespaces, system and user tables, views, and stored programs (stored procedures and functions, triggers, Event Scheduler events). The server also removes files that previously were used for metadata storage. For example, after upgrading from MySQL 5.7 to to MySQL 8.0, you will notice that your tables no longer have .frm files.

If this step succeeds, the server performs a cleanup:

If this step fails, the server reverts all changes to the data directory. In this case, you should remove all redo log files, start your MySQL 5.7 server on the same data directory, and fix the cause of any errors. Then perform another slow shutdown of the 5.7 server and start the MySQL 8.0 server to try again.

After the MySQL 8.0 server starts successfully, execute mysql_upgrade:

mysql_upgrade -u root -p

mysql_upgrade examines all tables in all databases for incompatibilities with the current version of MySQL. It makes any remaining changes required in the mysql system database between MySQL 5.7 and MySQL 8.0, so that you can take advantage of new privileges or capabilities. mysql_upgrade also brings the Performance Schema, INFORMATION_SCHEMA, and sys schema objects up to date for MySQL 8.0.

Shut down and restart the MySQL server to ensure that any changes made to the system tables take effect. For example:

mysqladmin -u root -p shutdown
mysqld_safe --user=mysql --datadir=/path/to/existing-datadir

The first time you started the MySQL 8.0 server (in an earlier step), you may have noticed messages written to the error log regarding nonupgraded tables. If mysql_upgrade has been run successfully, there should be no such messages the second time you start the server.

Review the information in Section 2.11.1.1, “Before You Begin”.

Export your existing data from the previous MySQL installation:

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

Shut down the old MySQL server. For example:

mysqladmin -u root -p shutdown

Install MySQL 8.0. For installation instructions, see Chapter 2, Installing and Upgrading MySQL.

Initialize a new data directory, as described in Section 2.10.1, “Initializing the Data Directory”. For example:

mysqld --initialize --datadir=/path/to/8.0-datadir

Copy the temporary 'root'@'localhost' password displayed to your screen or written to your error log for later use.

Start the MySQL 8.0 server, using the new data directory. For example:

mysqld_safe --user=mysql --datadir=/path/to/8.0-datadir

Reset the root password:

shell> mysql -u root -p
Enter password: ****  <- enter temporary root password

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

mysql -u root -p --force < data-for-upgrade.sql

Run mysql_upgrade. For example:

mysql_upgrade -u root -p

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

Shut down and restart the MySQL server to ensure that any changes made to the system tables take effect. For example:

mysqladmin -u root -p shutdown
mysqld_safe --user=mysql --datadir=/path/to/8.0-datadir