Skip to content
logo
Percona Server for MySQL
Upgrade using Standalone Packages
Initializing search
    percona/psmysql-docs
    percona/psmysql-docs
    • Home
      • The Percona XtraDB storage engine
      • List of features available in Percona Server for MySQL releases
      • Percona Server for MySQL feature comparison
      • Changed in Percona Server 8.0
      • Understand version numbers
      • Install Percona Server for MySQL
        • Install using APT repository
        • Files in DEB package
        • Build APT packages
        • Install from downloaded DEB packages
        • Apt pinning
        • Run Percona Server for MySQL
        • Uninstall
        • Install using a RPM repository
        • Files in RPM package
        • Install from downloaded RPM packages
        • Run Percona Server for MySQL
        • Uninstall
        • Install with binary tarballs
        • Binary tarballs available
        • Install Percona Server for MySQL from a source tarball
        • Compile Percona Server for MySQL 8.0 from source
      • Post-installation
      • Percona Server for MySQL in-place upgrading guide: from 5.7 to 8.0
      • Upgrade using the Percona repositories
      • Upgrade from systems that use the MyRocks or TokuDB storage engine and partitioned tables
      • Upgrade using Standalone Packages
        • DEB-based distributions
        • RPM-based distributions
      • Downgrade Percona Server for MySQL
      • Running Percona Server for MySQL in a Docker Container
      • Docker environment variables
      • Improved InnoDB I/O scalability
      • Adaptive network buffers
      • Multiple page asynchronous I/O requests
      • Thread pool
      • XtraDB performance improvements for I/O-bound highly-concurrent workloads
      • Prefix index queries optimization
      • Limit the estimation of records in a Query
      • Jemalloc memory allocation profiling
      • The ProcFS plugin
      • Binary logs and replication improvements
      • Compressed columns with dictionaries
      • Extended SELECT INTO OUTFILE/DUMPFILE
      • Extended SET VAR optimizer hint
      • Improved MEMORY storage engine
      • Suppress warning messages
      • Limiting the disk space used by binary log files
      • Support for PROXY protocol
      • SEQUENCE_TABLE(n) function
      • Slow query log rotation and expiration
      • Trigger updates
      • Extended mysqlbinlog
      • Extended mysqldump
      • InnoDB full-text search improvements
      • Too many connections warning
      • Handle corrupted tables
      • Percona Toolkit UDFs
      • Kill idle transactions
      • XtraDB changed page tracking
      • Enforcing storage engine
      • Expanded fast index creation
      • Backup locks
      • Audit log plugin
      • Start transaction with consistent snapshot
      • Extended SHOW GRANTS
      • Utility user
      • Working with SELinux
      • Working with AppArmor
      • PAM authentication plugin
      • Server variables
      • SSL improvements
      • Data masking
        • Using LDAP authentication plugins
        • LDAP authentication plugin system variables
        • Data at Rest Encryption
        • Use the keyring component or keyring plugin
          • Using the Key Management Interoperability Protocol (KMIP)
          • Use the Amazon Key Management Service (AWS KMS)
          • FIDO authentication plugin
        • Encryption functions
        • Encrypt File-Per-Table Tablespace
        • Encrypt schema or general tablespace
        • Encrypt system tablespace
        • Encrypt temporary files
        • Encrypt Binary Log Files and Relay Log Files
        • Encrypting the Redo Log data
        • Encrypt the undo tablespace
        • Rotate the master key
        • Advanced encryption key rotation
        • Encrypt doublewrite buffers
        • Verify the encryption for tables, tablespaces, and schemas
      • User statistics
      • Slow query log
      • Extended show engine InnoDB status
      • Show storage engines
      • Process list
      • Misc. INFORMATION_SCHEMA tables
      • Thread based profiling
      • InnoDB page fragmentation counters
      • Stacktrace
      • Libcoredumper
      • Manage group replication flow control
      • Group replication system variables
      • Percona MyRocks introduction
      • Percona MyRocks installation guide
      • Updated supported features
      • MyRocks limitations
      • Differences between Percona MyRocks and Facebook MyRocks
      • MyRocks Information Schema tables
      • MyRocks server variables
      • MyRocks status variables
      • Gap locks detection
      • Data loading
      • Installing and configuring Percona Server for MySQL with ZenFS support
      • TokuDB introduction
      • TokuDB installation
      • Use TokuDB
      • Fast updates with TokuDB
      • TokuDB files and file types
      • TokuDB file management
      • TokuDB background ANALYZE TABLE
      • TokuDB variables
      • TokuDB status variables
      • TokuDB fractal tree indexing
      • TokuDB troubleshooting
      • TokuDB Performance Schema integration
      • Frequently asked questions
      • Migrate and removing the TokuDB storage engine
      • Percona TokuBackup
      • Release notes index
      • Percona Server for MySQL 8.0.32-24 (2023-03-20)
      • Percona Server for MySQL 8.0.31-23 (2023-02-09)
      • Percona Server for MySQL 8.0.30-22 Update (2022-11-21)
      • Percona Server for MySQL 8.0.30-22 (2022-11-21)
      • Percona Server for MySQL 8.0.29-21 (2022-08-08)
      • Percona Server for MySQL 8.0.28-20 (2022-06-20)
      • Percona Server for MySQL 8.0.28-19 (2022-05-12)
      • Percona Server for MySQL 8.0.27-18 (2022-03-02)
      • Percona Server for MySQL 8.0.26-17 (2022-01-26)
      • Percona Server for MySQL 8.0.26-16 (2021-10-20)
      • Percona Server for MySQL 8.0.25-15 (2021-07-13)
      • Percona Server for MySQL 8.0.23-14 (2021-05-12)
      • Percona Server for MySQL 8.0.22-13 (2020-12-14)
      • Percona Server for MySQL 8.0.21-12 (2020-10-13)
      • Percona Server for MySQL 8.0.20-11 (2020-07-21)
      • Percona Server for MySQL 8.0.19-10 (2020-03-23)
      • Percona Server for MySQL 8.0.18-9
      • Percona Server for MySQL 8.0.17-8
      • Percona Server for MySQL 8.0.16-7
      • Percona Server for MySQL 8.0.15-6
      • Percona Server for MySQL 8.0.15-5
      • Percona Server for MySQL 8.0.14
      • Percona Server for MySQL 8.0.13-4
      • Percona Server for MySQL 8.0.13-3
      • Percona Server for MySQL 8.0.12-2rc1
      • List of variables introduced in Percona Server for MySQL 8.0
      • Development of Percona Server for MySQL
      • Trademark policy
      • Index of INFORMATION_SCHEMA tables
      • Frequently asked questions
      • Copyright and licensing information
      • Glossary

    • DEB-based distributions
    • RPM-based distributions

    Upgrade using Standalone Packages¶

    DEB-based distributions¶

    1. Make a full backup (or dump if possible) of your database. Move the database configuration file, my.cnf, to another direction to save it.

    2. Stop the server with /etc/init.d/mysql stop.

    3. Remove the installed packages with their dependencies: apt-get autoremove percona-server percona-client

    4. Do the required modifications in the database configuration file my.cnf.

    5. Download the following packages for your architecture:

      • percona-server-server

      • percona-server-client

      • percona-server-common

      • libperconaserverclient21

      The following example will download Percona Server for MySQL 8.0.29-21 release packages for Debian 11.0:

      $ wget https://downloads.percona.com/downloads/Percona-Server-LATEST/Percona-Server-8.0.29-21/binary/debian/bullseye/x86_64/Percona-Server-8.0.29-21-rc59f87d2854-bullseye-x86_64-bundle.tar
      
    6. Unpack the bundle to get the packages: tar xvf Percona-Server-8.0.29-21-rc59f87d2854-bullseye-x86_64-bundle.tar

      After you unpack the bundle, you should see the following packages:

      $ ls *.deb
      
      llibperconaserverclient21-dev_8.0.29-21-1.bullseye_amd64.deb  
      percona-server-dbg_8.0.29-21-1.bullseye_amd64.deb
      libperconaserverclient21_8.0.29-21-1.bullseye_amd64.deb      
      percona-server-rocksdb_8.0.29-21-1.bullseye_amd64.deb
      percona-mysql-router_8.0.29-21-1.bullseye_amd64.deb
      percona-server-server_8.0.29-21-1.bullseye_amd64.deb
      percona-server-client_8.0.29-21-1.bullseye_amd64.deb     
      percona-server-source_8.0.29-21-1.bullseye_amd64.deb
      percona-server-common_8.0.29-21-1.bullseye_amd64.deb     
      percona-server-test_8.0.29-21-1.bullseye_amd64.deb
      
    7. Install Percona Server for MySQL:

      $ sudo dpkg -i *.deb
      

      This will install all the packages from the bundle. Another option is to download/specify only the packages you need for running Percona Server for MySQL installation (libperconaserverclient21_8.0.13-3.stretch_amd64.deb, percona-server-client-8.0.13-3.stretch_amd64.deb, percona-server-common-8.0.13-3.stretch_amd64.deb, and percona-server-server-8.0.13-3.stretch_amd64.deb. Optionally you can install percona-server-tokudb-8.0.13-3.stretch_amd64.deb if you want TokuDB storage engine).

      Warning

      When installing packages manually, you must resolve all the dependencies and install missing packages yourself. At least the following packages should be installed before installing Percona Server for MySQL 8.0: * libmecab2, * libjemalloc1, * zlib1g-dev, * libaio1.

    8. Running the upgrade:

      Starting with Percona Server 8.0.16-7, the mysql_upgrade is deprecated. The functionality was moved to the mysqld binary which automatically runs the upgrade process, if needed. If you attempt to run mysql_upgrade, no operation happens and the following message appears: “The mysql_upgrade client is now deprecated. The actions executed by the upgrade client are now done by the server.” To find more information, see MySQL Upgrade Process Upgrades

      If you are upgrading to a Percona Server for MySQL version before 8.0.16-7, the installation script will NOT run automatically mysql_upgrade. You must run the mysql_upgrade manually.

      $ mysql_upgrade
      
      Checking if update is needed.
      Checking server version.
      Running queries to upgrade MySQL server.
      Checking system database.
      mysql.columns_priv                                 OK
      mysql.db                                           OK
      mysql.engine_cost                                  OK
      ...
      Upgrade process completed successfully.
      Checking if update is needed.
      
    9. Restart the service with service mysql restart.

    After the service has been successfully restarted you can use the new Percona Server for MySQL 8.0.

    RPM-based distributions¶

    1. Make a full backup (or dump if possible) of your database. Move the database configuration file, my.cnf, to another direction to save it.

    2. Stop the server with /etc/init.d/mysql stop.

    3. Check the installed packages:

      $ rpm -qa | grep percona-server
      
      Expected output
      percona-server-shared-8.0.29-21.1.el8.x86_64
      percona-server-shared-compat-8.0.29-21.1.el8.x86_64
      percona-server-client-8.0.29-21.1.el8.x86_64
      percona-server-server-8.0.29-21.1.el8.x86_64
      

      You may have the shared-compat package, which is required for compatibility.

    4. Remove the packages without dependencies with rpm -qa | grep percona-server | xargs rpm -e --nodeps.

      It is important that you remove the packages without dependencies as many packages may depend on these (as they replace mysql) and will be removed if omitted.

      Substitute grep ‘^mysql-‘ for grep ‘Percona-Server’ in the previous command and remove the listed packages.

    5. Download the packages of the desired series for your architecture from the download page. The easiest way is to download the bundle which contains all the packages. The following example will download Percona Server for MySQL 8.0.13-3 release packages for CentOS 7:

      $ wget https://downloads.percona.com/downloads/Percona-Server-LATEST/Percona-Server-8.0.29-21/binary/redhat/8/x86_64/Percona-Server-8.0.29-21-rc59f87d2854-el8-x86_64-bundle.tar
      
    6. Unpack the bundle to get the packages

      $ tar xvf Percona-Server-8.0.29-21-rc59f87d2854-el8-x86_64-bundle.tar
      

      After you unpack the bundle, you should see the following packages: ls \*.rpm

    7. Install Percona Server for MySQL:

      $ rpm -ivh percona-server-server-8.0.29-21.1.el8.x86_64.rpm \
      > percona-server-client-8.0.29-21.1.el8.x86_64.rpm \
      > percona-server-shared-8.0.29-21.1.el8.x86_64.rpm \
      > percona-server-shared-compat-8.0.29-21.1.el8.x86_64.rpm
      

      This command will install only packages required to run the Percona Server for MySQL 8.0. Optionally you can install the TokuDB storage engine by adding the percona-server-tokudb-8.0.13-3.el7.x86_64.rpm to the command above. You can find more information on how to install and enable the TokuDB storage in the TokuDB Installation guide.

    8. You can install all the packages (for debugging, testing, etc.) with rpm -ivh \*.rpm.

      Note

      When manually installing packages, you must resolve all the dependencies and install missing ones.

    9. Modify your configuration file, my.cnf, and install the plugins if necessary. If you are using the TokuDB storage engine you must comment out all the TokuDB specific variables in your configuration file(s) before starting the server, otherwise, the server will not start. RHEL/CentOS 7 automatically backs up the previous configuration file to /etc/my.cnf.rpmsave and installs the default my.cnf. After the upgrade/install process completes you can move the old configuration file back (after you remove all the unsupported system variables).

    10. As the schema of the grant table has changed, the server must be started without reading them with service mysql start.

    11. Running the upgrade:

      Starting with Percona Server 8.0.16-7, the mysql_upgrade is deprecated. The functionality was moved to the mysqld binary which automatically runs the upgrade process if needed. If you attempt to run mysql_upgrade, no operation happens and the following message appears: “The mysql_upgrade client is now deprecated. The actions executed by the upgrade client are now done by the server.” To find more information, see MySQL Upgrade Process Upgrades

      If you are upgrading to a Percona Server for MySQL version before 8.0.16-7, run mysql_upgrade to migrate to the new grant tables. mysql_upgrade will rebuild the required indexes and do the required modifications.

    12. Restart the server with service mysql restart.

      After the service has been successfully restarted you can use the new Percona Server for MySQL 8.0.

    Contact us

    For free technical help, visit the Percona Community Forum.

    To report bugs or submit feature requests, open a JIRA ticket.

    For paid support and managed or consulting services , contact Percona Sales.


    Last update: 2023-01-12
    Percona LLC and/or its affiliates, © 2023
    Made with Material for MkDocs

    Cookie consent

    We use cookies to recognize your repeated visits and preferences, as well as to measure the effectiveness of our documentation and whether users find what they're searching for. With your consent, you're helping us to make our documentation better.