Upgrading MySQL Binary or Package-based Installations on Unix/Linux 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. •As of MySQL 8.0.16, the server does so as part of the previous step, making any 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. It also brings the Performance Schema,  INFORMATION_SCHEMA , and sys  databases up to date for MySQL 8.0, and examines all user databases for incompatibilities with the current version of MySQL. 9. In the previous step, the server upgrades the data dictionary as necessary. Now it is necessary to perform any remaining upgrade operations: •Prior to MySQL 8.0.16, the server upgrades only the data dictionary in the previous step. After the MySQL 8.0 server starts successfully, execute  mysql_upgrade  to perform the remaining upgrade tasks: Then shut down and restart the MySQL server to ensure that any changes made to the system tables take effect. For example: The first time you start the MySQL 8.0 server (in an earlier step), you may notice messages in 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. The upgrade process does not upgrade the contents of the time zone tables. For upgrade instructions, see Section 5.1.15, “MySQL Server Time Zone Support” . If the upgrade process uses  mysql_upgrade  (that is, prior to MySQL 8.0.16), the process does not upgrade the contents of the help tables, either. For upgrade instructions in that case, see Section 5.1.17, “Server-Side Help Support” . A logical upgrade involves exporting SQL from the old MySQL instance using a backup or export utility such as  mysqldump  or  mysqlpump , installing the new MySQL server, and applying the SQL to your new MySQL instance. For details about what may need upgrading, see Section 2.11.3, “What the MySQL Upgrade Process Upgrades” . For some Linux platforms, MySQL installation from RPM or Debian packages includes systemd support for managing MySQL server startup and shutdown. On these platforms,  mysqld_safe  is not installed. In such cases, use systemd for server startup and shutdown instead of the methods used in the following instructions. See Section 2.5.9, “Managing MySQL Server with systemd” . Applying SQL extracted from a previous MySQL release to a new MySQL release may result in errors due to incompatibilities introduced by new, changed, Warning Note Logical Upgrade Note mysql_upgrade -u root -p mysqladmin -u root -p shutdown mysqld_safe --user=mysql --datadir= /path/to/existing-datadir  & 288