Before performing any update to MySQL, follow carefully
the instructions in Section 2.11.1, “Upgrading MySQL”. Among
other instructions discussed there, it is especially
important to back up your database before the update.

Selecting a Target Series

By default, the MySQL Yum repository updates MySQL to the
latest version in the release series you have chosen
during installation (see
Selecting a Release Series for details),
which means, for example, a 5.6.x
installation will NOT be updated to a 5.7.x
release automatically. To update to another release
series, you need to first disable the subrepository for
the series that has been selected (by default, or by
yourself) and enable the subrepository for your target
series. To do that, see the general instructions given in
Selecting a Release Series. For upgrading
from MySQL 5.6 to 5.7, perform
the reverse of the steps illustrated
in Selecting a Release Series, disabling the
subrepository for the MySQL 5.6 series and
enabling that for the MySQL 5.7 series.

As a general rule, to upgrade from one release series to
another, go to the next series rather than skipping a
series. For example, if you are currently running MySQL
5.5 and wish to upgrade to 5.7, upgrade to
MySQL 5.6 first before upgrading to
5.7.

You can also update only a specific component. Use the following
command to list all the installed packages for the MySQL
components (for dnf-enabled systems, replace
yum in the command with
dnf):

sudo yum list installed | grep "^mysql"

After identifying the package name of the component of your
choice, for platforms that are not dnf-enabled, update the
package with the following command, replacing
package-name with the name of the
package:

sudo yum update package-name

For dnf-enabled platforms:

sudo dnf upgrade package-name

Upgrading the Shared Client Libraries

After updating MySQL using the Yum repository, applications
compiled with older versions of the shared client libraries
should continue to work.

If you recompile applications and dynamically link
them with the updated libraries: As typical with new
versions of shared libraries where there are differences or
additions in symbol versioning between the newer and older
libraries (for example, between the newer, standard
5.7 shared client libraries and some
older—prior or variant—versions of the shared
libraries shipped natively by the Linux distributions' software
repositories, or from some other sources), any applications
compiled using the updated, newer shared libraries will require
those updated libraries on systems where the applications are
deployed. And, as expected, if those libraries are not in place,
the applications requiring the shared libraries will fail. So,
be sure to deploy the packages for the shared libraries from
MySQL on those systems. You can do this by adding the MySQL Yum
repository to the systems (see Adding the MySQL Yum Repository)
and install the latest shared libraries using the instructions
given in Installing Additional MySQL Products and Components with Yum.