Linux-UNIX: Managing an RPM- or shell-installed S-TAP during a major upgrade of the database server operating system
When you upgrade the operating system on your database server, you need to uninstall the S-TAP, and install a new version. However, most operating systems do not support a major upgrade, for example, from RHEL7 to RHEL8.
The appropriate target upgrade shell or RPM bundles must be available on the database. The build number of each bundle must be the same or greater than the bundle that is installed. Download from Fix Central.
Before you begin
If you cannot upgrade the operating system, you must uninstall the S-TAP, install the new operating system, and install the S-TAP bundle that is compatible with the newly installed operating system.
About this task
- Log in to the database.
- If the system uses A-TAP: Disable and deinstrument the A-TAP by using the guardctl utility.
- Uninstall the S-TAP, which also uninstalls the K-TAP.
- Upgrade the operating system on your database server. (Upgrading includes at least one
reboot of the operating system.) Note: Before you reboot, make sure to set the ktap_installed parameter to 1.
- Install the S-TAP and the K-TAP with the appropriate installer. For example, if you are upgrading from RHEL7 to RHEL8, you used the RHEL7 to uninstall the S-TAP in step 3, but you need the RHEL8 installer to install the new S-TAP.
- If the system uses A-TAP: Instrument and enable the A-TAP by using the guardctl utility.