Windows: Managing S-TAP when upgrading your database operating system
Use these guidelines for managing an S-TAP, when upgrading the operating system (OS) of your database. This is relevant for all S-TAPs, regardless of the installation method.
Before you begin
- Verify that the installed Windows S-TAP agent supports the new OS version. If not, upgrade Windows S-TAP before or after upgrading the OS, using the same method as the S-TAP installation. See the Guardium support matrix.
About this task
The GIM parameter auto_install_on_db_server_os_upgrade controls GIM's ability to auto-upgrade all bundles. If enabled, when the database server boots up after an operating system upgrade, GIM automatically downloads and installs these bundles. This parameter is disabled by default to prevent unintentional bundle upgrades. It's easiest to enable the parameter before you upgrade the database operating system.
If the parameter is disabled when you upgrade the database operating system, the GIM client detects
that the operating system changed, and it changes the _x suffix of the version to _0. You can see
the version in the Set up by Client, for example, 10.6.1.4_r123456_0. To
resolve the mismatch between the GIM client and the
database operating system, do one of:
- Enable the GIM global parameter auto_install_on_db_server_os_upgrade, which automatically upgrades all the GIM clients with the latest bundle of the operating system they support.
- Do not enable auto_install_on_db_server_os_upgrade, and upgrade the GIM clients manually.
Procedure
- Back up the guard_tap.ini file. You probably won't need it, but retain it until the S-TAP is functioning as expected after the upgrade.
- Upgrade the operating system of the database.
- Restart Windows S-TAP.