IBM Support

Release of Guardium Data Protection Windows GIM 12.2.2.259

Release Notes


Abstract

This technical note provides guidance for installing IBM Guardium Data Protection Windows Agents 12.2.2.259, including any new features or enhancements, resolved or known issues, or notices associated with the patch.

Content

Patch information
Product:IBM Guardium
Release version:Guardium 12.2 Windows Guardium Installation Manager (GIM)
Completion date:31 March 2026
 
 
Fix IDs
GIM-Installer-12.2_r120202259_1

 

 
Finding the patch
  1. Select the following options to download this patch on the IBM Fix Central website and click Continue.
    • Product selector: IBM Security Guardium
    • Installed Version: 12.2
    • Platform: Windows
  2. On the "Identify fixes" page, select Browse for fixes and click Continue.
  3. On the "Select fixes" page, select Database Agent (STAP, GIM and CAS). Then, enter the patch information in the Filter fix details field to locate the patch.
 
Attention
 
SHA256 GIM client certificates
Guardium 12.2.2.259 supports both SHA256 and SHA128 GIM certificates. This has the following implications:
  • The default certificates could be either SHA256 or SHA128, depending on the GIM server certificate setup. Custom certificates that use SHA256 are more secure and are recommended for GIM connections.
  • If your existing GIM clients have the latest GIM bundle installed, you can switch the GIM server certificate between default SHA256 and SHA128 by using the CLI command if needed. GIM connectivity is not interrupted by this switch.
  • Guardium 12.2.2.259 GIM only verifies bundles signed with SHA256 and requires installation of a transitional GIM bundle to support the GIM client upgrade from the SHA128 signed version to 12.2.2.259
 
 
GIM client to connect with default certificates if custom certificates fail
In the event that a connection between GIM and the Guardium server cannot be established by using custom certificates, GIM will use default certificates.
 

Single-stream agent releases 
Starting with Guardium Data Protection 12.2.1.0, most of the Linux-UNIX and Windows agents for Guardium Data Protection versions 12.0 and later are now released in a "single stream". Previously, each Guardium 12.x release (12.0, 12.1, and 12.2) had its own separate agent installers and patch packages. With the move to single-stream packaging, the agent binaries are unified into one continuous release line, so the same installation and upgrade package applies across multiple Guardium 12.x versions. This simplifies maintenance, reduces version divergence, and ensures consistent feature and fix availability across all supported 12.x environments. 

File names starting with 12.x are now applicable to all current Guardium 12.x versions (12.0, 12.1, and 12.2), and future releases within the Guardium 12.x family. The single-stream packaging currently applies to the following agents: 

  • Guardium Configuration Auditing System (CAS)
  • Guardium File Activity Monitor (FAM) for Windows
  • Guardium Installation Manager (GIM)
  • Guardium Software TAP (S-TAP)


With this change, customers no longer need to locate version-specific agent packages for each 12.x release. Installing the latest 12.x agent package will be supported across all 12.x collector and aggregator versions that meet the documented compatibility requirements.  

Note: The single-stream packaging does not currently apply to External S-TAP agents. 

For more information, see Single-stream agent releases.
 
 
 
Resolved issues
 
Guardium Windows GIM 12.2.2.259

No changes were made to Guardium Windows GIM 12.2.2.259 since Guardium Windows GIM 12.2.1.205 (see release note). If Guardium Windows GIM 12.2.1.205 is currently installed, upgrading to Guardium Windows GIM 12.2.2.259 is optional.

 

Guardium Windows GUC 12.2.1.121 

No changes were made to Guardium Windows GUC 12.2.1.121 since Guardium Windows GUC 12.0.0.140. If Guardium Windows GUC 12.0.0.140 is currently installed, upgrading to Guardium Windows GUC 12.2.1.121 is optional.

 
 
Known issues and workarounds
Issue key
Description
GRD-120773

Guardium Installation Manager (GIM) does not clean up leftover OpenSSL files in subfolder structure from previous installations. 

Workaround: Manually remove the leftover files.

GRD-121825

GIM upgrades fail on environments with SAML authentication enabled when the GIM_DEBUG=1 parameter is set, becoming stuck in 'In Progress' state before failing with a 'package verification failed' error. This is caused by excessive debug logging that results in timeout during package verification.

Workaround: Ensure GIM_DEBUG is set to 0 before performing the GIM upgrade.

 
 
Installers with MD5Sums
MD5SumFile name
405c5a32d709d0a9e18d8014579bc0bbGIM-Installer-12.2_r120202259_1.z
b43baa57cb486072d864b636e09bf18dguard-GIM-12.2_r120202259_1-x86_x64.gim
8ddfa3ed2b87804f7adb6492ce6c53feguard-GIM-guardium_12.2_r120202259_1-Windows-Server-Windows-x86_x64.exe.signed
da537f7ca6ec33bef3abf5422d4b0789guard-GIM_transitional-12.2_r120202259_1-x86_x64.gim
92eca1c385558ed9cd6679dd4f85c37fguard-GUC-12.2_r120200121_1-x86_x64.gim
a43795209e9ad8113a29eb73f5caee58guard-GUC-guardium_12.2_r120200121_1-Windows-Server-Windows-x86_x64.exe.signed
 
 
Related Guardium updates
  • Guardium Data Protection 12.2.2 (see release note)
  • Guardium Data Protection Windows CAS 12.2.2.259 (see release note)
  • Guardium Data Protection Windows FamMonitor 12.2.2.259 (see release note)
  • Guardium Data Protection Windows S-TAP 12.2.2.259 (see release note)
 

[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"ARM Category":[{"code":"a8m0z000000Gp0TAAS","label":"GIM"},{"code":"a8m3p000000PCTuAAO","label":"Platform\/Installation\/Deployment"}],"ARM Case Number":"","Platform":[{"code":"PF033","label":"Windows"}],"Version":"12.2.0"}]

Document Information

Modified date:
31 March 2026

UID

ibm17267965

Page Feedback