Linux-UNIX: Upgrading S-TAP using RPM

Edit online

Before you begin

Obtain the correct S-TAP® installer script, from either Fix Central, or your Guardium representative. The script name identifies the database server operating system.
Note: Certain Guardium® Data ProtectionS-TAP updates combined with certain sniffer patches do not support the ability to transfer DB_USER in the event of a failover. Make sure that you have installed compatible patches, as described in Determining whether Guardium Data Protection Linux/UNIX S-TAP and Sniffer patches are compatible.

About this task

RPM names have the format: guard-stap-10.6.0.0.89165-1-rhel-6-linux-x86_64.x86_64.rpm, where the first three numbers are the release number of STAP (10.0.0, 10.1.2, etc) and the fourth number is the code revision (89165). The number immediately following is the package iteration which would increment in the case of adding K-TAP modules to the RPM.

There is a single RPM for the 32-bit S-TAPs and two RPMs for the 64-bit S-TAPs so that the 64-bit S-TAP does not have a dependency on 32-bit libraries if 32-bit exit libraries are not required. The extra RPM looks like guard-stap-32bit-exit-libs-10.1.0.89165-1-rhel-6-linux-x86_64.x86_64.rpm and has a dependency on the main RPM.

RPM logs are saved to /opt/guardium/rpm_logs

You can run the guard-config-update script as root user or a non-root user. Use the help command to see your permitted functions.

All S-TAP configuration persists during the upgrade.

Procedure

  1. Unzip the S-TAP package and copy the RPM to /opt/guardium of the database server.
  2. Run the command: rpm -U <RPM_NAME>.
    If you want to modify the FlexLoad mechanism value, include the parameter in the rpm command: --set-flexload, where 0 disables the feature, and 1 enables it.

What to do next

After the upgrade completes, verify S-TAP status:
  • Verify that the row of the S-TAP has a green status (first column) in Monitor > Maintenance > S-TAP Logs > S-TAP Staus