Linux-UNIX: Installing, upgrading and uninstalling S-TAP agents

There are a few methods of installing, upgrading and uninstalling S-TAPs. Learn about each one and understand what works best for you.

Linux-UNIX: Install S-TAP agents installation flow
Verify prerequisites, then install an S-TAP on Linux, Solaris, AIX and HP-UX servers using the Deploy Monitoring Agents tool, Guardium Installation Manager (GIM), the RPM, or the shell installer.
Linux-UNIX: S-TAP installation prerequisites
Verify all prerequisites before starting your S-TAP installation.
Linux-UNIX: Before you start installing S-TAP
Read these notes before you start to install an S-TAP®.
Linux-UNIX: Use GIM to install, upgrade, uninstall the S-TAP
Linux-UNIX: Use RPM to install, upgrade, uninstall the S-TAP
You can manage your S-TAP agent with .rpm on RHEL and for SUSE Linux databases.
Linux-UNIX: Use shell installer to install, upgrade, uninstall the S-TAP
Linux-UNIX: Use native installers to install, upgrade, uninstall the S-TAP
The native installer provides a shell for the shell installer. The only advantage is that it ensures that S-TAP is registered in the operating system asset repository. This registration is not required by Guardium® for the installation of the S-TAP, but it might be a requirement at your company. Use the native installer only when necessary.
Linux-UNIX: S-TAP upgrade workflows per monitoring mechanism
The S-TAP upgrade workflow depends on your monitoring mechanism: K-TAP, exit library, A-TAP. Use these workflows together with the specific upgrade procedure.
Linux-UNIX: Working with K-TAP
K-TAP is a kernel module that is installed into the database server operating system during S-TAP installation. After it is installed, it can be enabled or disabled with a configuration file setting. When enabled, it observes access to a database server by hooking the mechanisms used to communicate between the database client and the server. With K-TAP you do not need to change how database clients connect to the server.
Linux-UNIX: Special environments configuration
Use these procedures for as relevant for systems with Zones, RAC, WPAR, clusters.
Linux-UNIX: What to restart or reboot on the database server after installing or updating S-TAP
This topic details what needs to be rebooted or restarted after you install or upgrade your UNIX or Linux S-TAP. Restart and reboot requirements are the same for GIM and non-GIM implementations.
Linux-UNIX: Managing a GIM-, RPM-, and shell-installed S-TAP during a database upgrade
Only the A-TAP needs handling when you upgrade a database with a GIM, RPM, or shell-installed UNIX S-TAP. If a system is running multiple databases, the S-TAP can continue to run and monitor all other databases not being upgraded.
Linux-UNIX: Managing GIM clients during a major upgrade of the database server operating system
When you upgrade the operating system on your database server, use the GIM client to automatically upgrade itself and the GIM bundles (for example, GIM, S-TAP, CAS) installed on the Linux-UNIX database. However, most operating systems do not support a major upgrade, for example from RHEL7 to RHEL8.
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.
Linux-UNIX: Managing a GIM-, RPM-, or shell-installed S-TAP during a minor or kernel upgrade of the database server operating system
A minor database operating system upgrade can include a new operating system kernel. Use this task for both a minor upgrade or a kernel upgrade.

Parent topic: Linux-UNIX: S-TAP user's guide