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.

Before you begin

  • The loader automatically picks the right K-TAP at boot time.
  • If the new kernel is already supported by a K-TAP module, the K-TAP installs as part of the S-TAP installation.
  • If the new kernel is not supported by a K-TAP module, then you must install the development packages that support a local K-TAP module build. You might need to request a new K-TAP module from IBM Support. Save the appropriate K-TAP module locally on the database. For more information, see Linux-UNIX: Preparing to install K-TAP.
  • The parameter auto_install_on_db_server_os_upgrade is not relevant in this scenario.

Procedure

  1. If the system uses A-TAP: Use the guardctl utility to disable and deinstrument the A-TAP.
  2. Upgrade the operating system or the kernel on your database server (upgrading includes rebooting the operating system.).
    Note: Before you reboot, make sure that the ktap_installed parameter in guard_tap.ini is set to 1.
  3. If the system uses A-TAP: Use guardctl to instrument and enable the A-TAP.