Upgrade procedures for 9.7¶

Topic type: Task

Need expert guidance for your Percona Server upgrade? Percona Support can help .

Use the following procedures to upgrade Percona Server for MySQL. The procedures cover Percona repositories (recommended), standalone packages, and both in-place and logical paths. For underlying MySQL guidance, see Upgrading MySQL Binary or Package-based Installations on Unix/Linux .

Critical

Always test the upgrade in a non-production environment first. For detailed procedures or troubleshooting, contact our Percona Support team .

Choose an upgrade method¶

Two methods apply to most 9.7 environments. Use the following table to choose the method that matches your downtime budget and data size.

Method	Description	Downtime	Best for
In-place	Stop the source server, replace binaries or packages, then restart on the existing data directory	Short, equal to restart and metadata upgrade time	Same-platform upgrades within Percona Server for MySQL
Logical	Export SQL from the source server, install 9.7 on a clean target, then load the dump	Long, scaled to data size	Cross-platform moves, storage-engine consolidations, or dump-based reorganizations

For a parallel environment with controlled cutover, see Upgrade strategies.

Prepare for the upgrade¶

Complete the following pre-flight steps before any procedure on this page.

Complete the pre-upgrade items in the upgrade checklist for 9.7.
Create a full backup or dump of your database. Verify the backup by restoring into a clean test environment.
Save a copy of the database configuration file (my.cnf) to a safe location.
Edit the configuration file before stopping the server. For example, remove deprecated variables and update settings for 9.7.
Run XA RECOVER against the source server. Commit or rollback any uncommitted XA transactions before continuing.
```
XA RECOVER;
```
If innodb_fast_shutdown is set to 2 (cold shutdown), reset to 1 or 0 before stopping. A fast or slow shutdown leaves InnoDB undo logs and data files in a state that is safe across releases.
```
SET GLOBAL innodb_fast_shutdown = 0;
```
Stop the server with the appropriate command for your system.
```
sudo systemctl stop mysql
```

If your prior installation comprises multiple Red Hat Package Manager (RPM) packages, upgrade every related package together. A partial upgrade leaves mismatched binaries.

Upgrade with Percona repositories (recommended)¶

The Percona repositories handle dependencies automatically and reduce upgrade complexity. The following documents describe how to enable the repositories:

DEB-based distributionsRPM-based distributions

Run the following commands as root or with sudo.

Create a full backup or dump of your database. Save a copy of the database configuration file, my.cnf, to another directory. Without a backup, the upgrade may overwrite the file.
Stop the server with the appropriate command for your system.
```
sudo systemctl stop mysql
```
Modify the database configuration file, my.cnf, as needed. For example, remove deprecated variables and update settings for 9.7.

Install Percona Server for MySQL.

sudo apt update
sudo apt install curl
curl -O https://repo.percona.com/apt/percona-release_latest.generic_all.deb
sudo apt install gnupg2 lsb-release ./percona-release_latest.generic_all.deb
sudo apt update
sudo percona-release setup ps-97-lts
sudo apt install percona-server-server

Install the storage engine packages.

If you used the MyRocks storage engine in the previous version, install the percona-server-rocksdb package.
```
sudo apt install percona-server-rocksdb
```
The mysqld binary runs the upgrade process automatically on first start. The server creates the data dictionary and refreshes the Performance Schema, INFORMATION_SCHEMA, and sys databases. The server then removes obsolete .frm files. For details, see MySQL Upgrade Process .
Restart the service.
```
sudo systemctl restart mysql
```

After a successful restart, you can use Percona Server for MySQL 9.7.

Run the following commands as root or with sudo.

Create a full backup or dump of your database. Save a copy of the database configuration file, my.cnf, to another directory.
Stop the server with the appropriate command for your system.
```
sudo systemctl stop mysql
```
Check your installed packages.
```
rpm -qa | grep Percona-Server
```
Remove the packages without dependencies. The command does not prompt for confirmation.
```
rpm -qa | grep Percona-Server | xargs rpm -e --nodeps
```

Remove the mysql-prefixed packages.

rpm -qa | grep '^mysql-' | xargs rpm -e --nodeps

Install the percona-server-server package.

sudo yum install https://repo.percona.com/yum/percona-release-latest.noarch.rpm
sudo percona-release setup ps-97-lts
sudo yum install percona-server-server

Install the storage engine packages.

If you used the MyRocks storage engine in the previous version, install the percona-server-rocksdb package.
```
sudo yum install percona-server-rocksdb
```
Modify your configuration file, my.cnf, as needed. For example, remove deprecated variables and update settings for 9.7. If you used plugins replaced by components in 9.7, plan the transition. See Upgrade from plugins to components for details.
The mysqld binary runs the upgrade process automatically on first start. The server creates the data dictionary and refreshes the Performance Schema, INFORMATION_SCHEMA, and sys databases. The server then removes obsolete .frm files. For details, see MySQL Upgrade Process .
Restart the server.
```
sudo systemctl restart mysql
```

After a successful restart, you can use Percona Server for MySQL 9.7.

Upgrade with standalone packages¶

Use standalone packages when repositories are unavailable, or when you must install from manually downloaded packages. Standalone installs require you to resolve dependencies yourself.

Debian-derived distributionsRed Hat-derived distributions

Remove the installed packages with their dependencies.

sudo apt autoremove percona-server percona-client

Modify the database configuration file, my.cnf, as needed.
Download the following packages for your architecture.
- libperconaserverclient21
- percona-server-client
- percona-server-common
- percona-server-server
The following example downloads Percona Server for MySQL 9.7.0-0 packages for Debian 11.0.
```
wget https://downloads.percona.com/downloads/Percona-Server-innovative-release/Percona-Server-9.7.0-0/binary/debian/bullseye/x86_64/Percona-Server-9.7.0-0-r582ebeef-bullseye-x86_64-bundle.tar
```

Unpack the bundle to get the packages.

tar xvf Percona-Server-9.7.0-0-r582ebeef-bullseye-x86_64-bundle.tar

After unpacking, you should see the following packages.

ls *.deb

Expected output

libperconaserverclient21-dev_9.7.0-0.bullseye_amd64.deb
percona-server-dbg_9.7.0-0.bullseye_amd64.deb
libperconaserverclient21_9.7.0-0.bullseye_amd64.deb
percona-server-rocksdb_9.7.0-0.bullseye_amd64.deb
percona-mysql-router_9.7.0-0.bullseye_amd64.deb
percona-server-server_9.7.0-0.bullseye_amd64.deb
percona-server-client_9.7.0-0.bullseye_amd64.deb
percona-server-source_9.7.0-0.bullseye_amd64.deb
percona-server-common_9.7.0-0.bullseye_amd64.deb
percona-server-test_9.7.0-0.bullseye_amd64.deb

Install Percona Server for MySQL.
```
sudo dpkg -i *.deb
```
The command installs all packages from the bundle. You can also install only the packages required to run Percona Server for MySQL.
- libperconaserverclient21_9.7.0-0.bullseye_amd64.deb
- percona-server-client_9.7.0-0.bullseye_amd64.deb
- percona-server-common_9.7.0-0.bullseye_amd64.deb
- percona-server-server_9.7.0-0.bullseye_amd64.deb
Warning

When you install packages manually, you must resolve all dependencies and install missing packages yourself. Install the following packages before installing Percona Server for MySQL 9.7.0-0.
- libaio1
- libjemalloc1
- libmecab2
- zlib1g-dev
The mysqld binary runs the upgrade process automatically on first start. For more information, see MySQL Upgrade Process .
Restart the service.
```
sudo service mysql restart
```

After a successful restart, use Percona Server for MySQL 9.7.0-0.

Check the installed packages.

rpm -qa | grep percona-server

Expected output

percona-server-shared-9.7.0-0.el9.x86_64
percona-server-shared-compat-9.7.0-0.el9.x86_64
percona-server-client-9.7.0-0.el9.x86_64
percona-server-server-9.7.0-0.el9.x86_64

The shared-compat package may also be present, which is required for compatibility.

Remove the packages without dependencies.
```
rpm -qa | grep percona-server | xargs rpm -e --nodeps
```
Use --nodeps because the Percona Server packages share dependencies. Without --nodeps, removing one package removes related packages.

Run the following command to remove mysql-prefixed packages.
```
rpm -qa | grep '^mysql-' | xargs rpm -e --nodeps
```
Download the packages for your architecture from the download page . The bundle includes all packages and is the recommended option. The following example downloads Percona Server for MySQL 9.7.0-0 packages for Red Hat Enterprise Linux (RHEL) 9.
```
wget https://downloads.percona.com/downloads/Percona-Server-9.7/Percona-Server-9.7.0-0/binary/redhat/9/x86_64/Percona-Server-9.7.0-0-r9927a2fb-el9-x86_64-bundle.tar
```
Unpack the bundle to get the packages.
```
tar xvf Percona-Server-9.7.0-0-r9927a2fb-el9-x86_64-bundle.tar
```
After unpacking, you should see the available packages.
```
ls *.rpm
```
Install Percona Server for MySQL.
```
sudo rpm -ivh percona-server-server-9.7.0-0.el9.x86_64.rpm \
percona-server-client-9.7.0-0.el9.x86_64.rpm \
percona-server-shared-9.7.0-0.el9.x86_64.rpm \
percona-server-shared-compat-9.7.0-0.el9.x86_64.rpm
```
The command installs only the packages required to run Percona Server for MySQL 9.7.0-0.

Run the following command to install all packages, including debugging and testing packages.
```
sudo rpm -ivh *.rpm
```
Note

When you install packages manually, you must resolve all dependencies and install missing packages.
Modify your configuration file, my.cnf, as needed. For example, remove deprecated variables and update settings for 9.7. If you used plugins replaced by components in 9.7, plan the transition. See Upgrade from plugins to components for details.

RHEL and its derivatives copy the previous configuration file to /etc/my.cnf.rpmsave. The package install also adds the default my.cnf. After the upgrade or install completes, restore your configuration from the saved copy. Remove any unsupported system variables before restoring.
The mysqld binary runs the upgrade process automatically on first start. For more information, see MySQL Upgrade Process .
Restart the server.
```
sudo service mysql restart
```

After a successful restart, you can use Percona Server for MySQL 9.7.0-0.

Perform a logical upgrade with mysqldump¶

Use a logical upgrade when an in-place upgrade is not viable. Examples include cross-platform migrations and storage-engine consolidations. The logical path exports SQL from the source server and loads the SQL into a fresh 9.7 server.

Run the following procedure on the source and target hosts.

Export the source database. Include --routines, --events, and --all-databases so that stored programs and the mysql system database appear in the dump.

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

Stop the source server.
```
mysqladmin -u root -p shutdown
```
Install Percona Server for MySQL 9.7 on a clean host or a separate path. Use the procedure in Upgrade with Percona repositories (recommended) or Upgrade with standalone packages.
Initialize a fresh data directory for 9.7.
```
mysqld --initialize --datadir=/var/lib/mysql-9.7
```
Capture the temporary root password from standard error or the error log.

Start the 9.7 server with the fresh data directory.

mysqld_safe --user=mysql --datadir=/var/lib/mysql-9.7 &

Connect with the temporary password and reset the root account.

ALTER USER USER() IDENTIFIED BY '<NEW_ROOT_PASSWORD>';

Load the dump file into the 9.7 server.

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

Restart with --upgrade=FORCE to finish data dictionary tasks.

mysqladmin -u root -p shutdown
mysqld_safe --user=mysql --datadir=/var/lib/mysql-9.7 --upgrade=FORCE &

Global Transaction Identifier (GTID) interaction

Do not load a dump file that contains the mysql system database when gtid_mode=ON. The mysqldump output issues data manipulation statements against MyISAM system tables. These statements conflict with the GTID requirement for transactional storage. Disable GTID functionality during the load or take the dump without system tables.

Validate after upgrading¶

After completing the upgrade, follow the post-upgrade validation steps in the upgrade checklist.

The upgrade does not refresh time zone tables. Reload the tables with mysql_tzinfo_to_sql if your applications depend on time zone names.

mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root -p mysql

Troubleshoot upgrade failures¶

The following table maps common upgrade failure modes to the corrective action.

Symptom	Diagnosis	Solution
The 9.7 server fails the metadata upgrade and reverts the data directory	A schema problem flagged during pre-upgrade checks was not resolved	Remove the redo log files (`ib_logfile*`) from the data directory. Start the source server on the same data directory. Fix the schema. Perform a slow shutdown with `innodb_fast_shutdown=0`, then retry the upgrade
`mysqld` does not start after binary replacement	A stale `my.cnf` from the prior installation is still in effect	Run `mysqld --print-defaults` to inspect the active defaults. Replace or repair the configuration file, then retry start
Compiled client programs report “Commands out of sync” or core dump	Programs are linked against the prior client headers and shared library	Recompile programs against the 9.7 headers (`mysql.h`) and the 9.7 shared client library. Note the major version change in the library file name
A loadable function and a built-in function share a name	The 9.7 server provides a built-in function that collides with an existing loadable function	Run `DROP FUNCTION <NAME>`. Recreate the function with `CREATE FUNCTION` under a non-conflicting name
Encrypted InnoDB tablespaces fail to open	The keyring component or plugin is not loaded early in the startup sequence	Configure the keyring through a manifest file (`mysqld.my`). See Upgrade from plugins to components

For schema-readiness checks before the upgrade, see Upgrade checklist for 9.7.