Installation & Upgrade & De-installation
This chapter describes all installation/upgrade/de-installation steps.
Last updated
This chapter describes all installation/upgrade/de-installation steps.
Last updated
Several playbooks are available and recommended for MariaDB prerequisites, source and DMK installation.
Please follow the instruction in Readme.md in dmk/ansible.
This paragraph describes all necessary steps which must be completed before you start the DMK installation.
The system must come with a perl installation
Execute the below command to check if perl is installed:
Otherwise install the following packages if needed.
Ensure the mysql.cnf configuration file exists
Based on the dbi services and OFA (Oracle Flexible Architecture) best practices extract the archive under ${MYQL_BASE}/local, as explained below:
Typically, ${MYSQL_BASE} match:
“/u01/app/mysql” on Linux/Unix
This is one of the most important installation steps, once extracted the “default” configuration file is available under ${DMK_HOME}/etc.
${DMK_HOME}/etc/dmk.conf.unix for Linux
Adapt the following variables
MYSQL_BASE, set it as explained in the OFA document
MYSQL_CNF, location of the mysql.cnf
Install DMK, from the ${DMK_HOME}/bin directory or with absolute path as follows:
Don’t be afraid, the installation is automated without questioning.
Congratulations you have successfully installed DMK!
DMK doesn’t only belong to a unique/specific user, if the necessary privileges are correctly distributed you can start DMK from another user as presented below.
Install and source DMK under the target user
Once installed it can be sourced using the DBA’s login profile
dbi services recommend to perform a backup of your DMK package before upgrading.
The upgrade process is similar to the installation except that the prerequisites are already fulfilled:
Extract the software as explained in chapter 3.1.3 Software extraction
Install DMK as explained in chapter 3.1.5 Install
That’s it!
This paragraph describes the de-installation of the DMK toolkit.
Do not forget to remove the profile from your environment.
During the installation, the “default**” configuration file ${DMK_HOME}/etc/dmk.conf.unix is renamed to dmk.conf**. This mechanism avoids any configuration loss in case of upgrades.
For Linux/Unix use the appropriate SHELL script :
Upgrades don’t affect the configuration file “${DMK_HOME}/etc/dmk.conf” file, please review this for newly introduced aliases or variables.
For Linux: