Upgrade to MariaDB Community Server 10.3 on SLES 12
These instructions detail the upgrade from a previous version of MariaDB Community Server to MariaDB Community Server 10.3 on SUSE Linux Enterprise Server 12.
When MariaDB Community Server is upgraded, the old version needs to be uninstalled, and the new version needs to be installed.
Occasionally, issues can be encountered during upgrades. These issues can even potentially corrupt the database's data files, preventing you from easily reverting to the old installation. Therefore, it is generally best to perform a backup prior to upgrading. If an issue is encountered during the upgrade, you can use the backup to restore your MariaDB Server database to the old version. If the upgrade finishes without issue, then the backup can be deleted.
Take a full backup:
$ sudo mariabackup --backup \ --user=mariabackup_user \ --password=mariabackup_passwd \ --target-dir=/data/backup/preupgrade_backup
Confirm successful completion of the backup operation.
The backup must be prepared:
$ sudo mariabackup --prepare \ --target-dir=/data/backup/preupgrade_backup
Confirm successful completion of the prepare operation.
Backups should be tested before they are trusted.
Uninstall the Old Version
When upgrading to a new major release of MariaDB Community Server, it is necessary to remove the existing installation of MariaDB Community Server, before installing the new version of MariaDB Community Server. Otherwise, the package manager will refuse to install the new version of MariaDB Community Server.
Stop the MariaDB Server Process
Before the old version can be uninstalled, we first need to stop the current MariaDB Server process.
Set the innodb_fast_shutdown system variable to
SET GLOBAL innodb_fast_shutdown = 1;
Use XA RECOVER to confirm that there are no external XA transactions in a prepared state:
Commit or rollback any open XA transactions before stopping the node for upgrade.
Stop the server process using the
$ sudo systemctl stop mariadb
Uninstall via ZYpp (SLES)
Uninstall all of the MariaDB Community Server packages. Note that a wildcard character is used to ensure that all MariaDB Community Server packages are uninstalled:
$ sudo zypper remove "MariaDB-*"
Be sure to check that this wildcard does not unintentionally refer to any of your custom applications.
Uninstall the Galera package as well.
The name of the package depends on the specific version of MariaDB Community Server.
When upgrading from MariaDB Community Server 10.4, the package is called
$ sudo zypper remove galera-4
When upgrading from MariaDB Community Server 10.3 or earlier, the package is called
$ sudo zypper remove galera
Before proceeding, verify that all MariaDB Community Server packages are uninstalled. The following command should not return any results:
$ rpm --query --all | grep -i -E "mariadb|galera"
Install the New Version
MariaDB Corporation provides a ZYpp package repository for SUSE Linux Enterprise Server 12.
Install via ZYpp (SLES)
Configure the ZYpp package repository.
To configure ZYpp package repositories:
$ sudo zypper install wget $ wget https://downloads.mariadb.com/MariaDB/mariadb_repo_setup $ echo "fd3f41eefff54ce144c932100f9e0f9b1d181e0edd86a6f6b8f2a0212100c32c mariadb_repo_setup" \ | sha256sum -c - $ chmod +x mariadb_repo_setup $ sudo ./mariadb_repo_setup \ --mariadb-server-version="mariadb-10.3"
Install MariaDB Community Server and package dependencies:
$ sudo zypper install MariaDB-server MariaDB-backup
Installation of additional packages may be required for some plugins.
Installation only loads MariaDB Community Server to the system. MariaDB Community Server requires configuration before the database server is ready for use.
For platforms that use YUM or ZYpp as a package manager:
MariaDB Community Server's packages bundle several configuration files:
If your version of any of these configuration files contained any custom edits, then the package manager may save your edited version with the
.rpmsave extension during the upgrade process. If you want to continue using your version with the custom edits, then you may need to move it back. For example, to move
server.cnf back in place:
$ sudo mv /etc/my.cnf.d/server.cnf /etc/my.cnf.d/server.cnf.original $ sudo mv /etc/my.cnf.d/server.cnf.rpmsave /etc/my.cnf.d/server.cnf
Starting the Server
MariaDB Community Server includes configuration to start, stop, restart, enable/disable on boot, and check the status of the Server using the operating system default process management system.
SUSE Linux Enterprise Server 12 uses systemd. You can manage the Server process using the
Enable during startup
Disable during startup
Upgrading the Data Directory
MariaDB Community Server 10.3 ships with the mysql_upgrade utility which can be used to identify and correct compatibility issues in the new version. After you upgrade your Server and start the server process, run this utility to upgrade the data directory:
$ sudo mysql_upgrade
When MariaDB Community Server is up and running on your system, you should test that it is working and there weren't any issues during startup.
Connect to the server using MariaDB Client using the
$ sudo mysql Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 9 Server version: 10.3.31-MariaDB MariaDB Server Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]>
The version of the server can be verified by checking the client's initial output.
SHOW GLOBAL VARIABLES LIKE 'version';
+---------------+-----------------+ | Variable_name | Value | +---------------+-----------------+ | version | 10.3.31-MariaDB | +---------------+-----------------+
You can also verify the server version by calling the VERSION() function:
+-----------------+ | VERSION() | +-----------------+ | 10.3.31-MariaDB | +-----------------+