MySQL 5.7 Reference Manual
MySQL 5.7 Release Notes
It is preferable to use the MySQL Yum repository or MySQL SLES Repository to upgrade MySQL on RPM-based platforms. However, if you have to upgrade MySQL using the RPM packages downloaded directly from the MySQL Developer Zone (see Section 7.5, “Installing MySQL on Linux Using RPM Packages from Oracle” for information on the packages), go to the folder that contains all the downloaded packages (and, preferably, no other RPM packages with similar names), and issue the following command:
yum install mysql-community-{server,client,common,libs}-*Replace yum with zypper for SLES systems, and with dnf for dnf-enabled systems.
While it is much preferable to use a high-level package management tool like yum to install the packages, users who preferred direct rpm commands can replace the yum install command with the rpm -Uvh command; however, using rpm -Uvh instead makes the installation process more prone to failure, due to potential dependency issues the installation process might run into.
For an upgrade installation using RPM packages, the MySQL server is automatically restarted at the end of the installation if it was running when the upgrade installation began. If the server was not running when the upgrade installation began, you have to restart the server yourself after the upgrade installation is completed; do that with, for example, the follow command:
service mysqld start
Once the server restarts, run mysql_upgrade to check and possibly resolve any incompatibilities between the old data and the upgraded software. mysql_upgrade also performs other functions; see mysql_upgrade — Check and Upgrade MySQL Tables for details.
Note
Because of the dependency relationships among the RPM packages, all of the installed packages must be of the same version. Therefore, always update all your installed packages for MySQL. For example, do not just update the server without also upgrading the client, the common files for server and client libraries, and so on.
Migration and Upgrade from installations by older RPM packages. Some older versions of MySQL Server RPM packages have names in the form of MySQL-* (for example, MySQL-server-* and MySQL-client-*). The latest versions of RPMs, when installed using the standard package management tool (yum, dnf, or zypper), seamlessly upgrade those older installations, making it unnecessary to uninstall those old packages before installing the new ones. Here are some differences in behavior between the older and the current RPM packages:
Table 10.1 Differences Between the Previous and the Current RPM Packages for Installing MySQL
| Feature | Behavior of Previous Packages | Behavior of Current Packages |
|---|---|---|
| Service starts after installation is finished | Yes | No, unless it is an upgrade installation, and the server was running when the upgrade began. |
| Service name | mysql | For RHEL, Oracle Linux, CentOS, and Fedora: mysqld For SLES: mysql |
| Error log file | At
/var/lib/mysql/ |
For RHEL, Oracle Linux, CentOS, and Fedora: at
For SLES: at
|
Shipped with the /etc/my.cnf file |
No | Yes |
| Multilib support | No | Yes |
Note
Installation of previous versions of MySQL using older
packages might have created a configuration file named
/usr/my.cnf. It is highly recommended
that you examine the contents of the file and migrate the
desired settings inside to the file
/etc/my.cnf file, then remove
/usr/my.cnf.
Upgrading to MySQL Enterprise Server. Upgrading from a community version to a commercial version of MySQL requires that you first uninstall the community version and then install the commercial version. In this case, you must restart the server manually after the upgrade.
Interoperability with operating system native MySQL packages.
Many Linux distributions ship MySQL as an integrated part of the
operating system. The latest versions of RPMs from Oracle, when
installed using the standard package management tool
(yum, dnf, or
zypper), seamlessly upgrades and replaces the
version of MySQL that comes with the operating system, and the
package manager automatically replaces system compatibility
packages such as
mysql-community-libs-compat with the
relevant new versions.
Upgrading from non-native MySQL packages. If you have installed MySQL with third-party packages NOT from your Linux distribution's native software repository (for example, packages directly downloaded from the vendor), you must uninstall all those packages before you can upgrade using the packages from Oracle.