IBM Support

Release of Guardium Data Protection universal connector patch 12.0p5002

Release Notes


Abstract

This technical note provides guidance for installing IBM Guardium Data Protection universal connector patch 12.0p5002, including any new features or enhancements, resolved or known issues, or notices associated with the patch.

Content

Patch information
  • Patch file name: SqlGuard-12.0p5002_UC_May_27_2025.tgz.enc.sig
  • MD5 checksum: e2ac0558a0b3862110c8b83c574c68b3
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.0
    • Platform: All
  2. On the "Identify fixes" page, select Browse for fixes and click Continue.
  3. On the "Select fixes" page, select Appliance patch (GPU and Ad-Hoc). Then, enter the patch information in the Filter fix details field to locate the patch.
For information about Guardium patch types and naming conventions, see the Understanding Guardium patch types and patch names support document.
Prerequisites
Guardium 12.0p35 (see release note) or later
Installation
Notes:
  • This patch is only for Guardium universal connector customers and can be installed on all releases of Guardium 12.x.
  • Starting with the release of 12.0p35 (see release note), Guardium Data Protection appliance bundle patches no longer include universal connector fixes.
  • Universal connector patches are cumulative, they contain all previous universal connector patches for that major version.
  • This patch restarts the Tomcat processes (through the CLI) .
Overview:
  1. Download the patch and extract the compressed package outside the Guardium system.
  2. Review the latest version of this patch release note just before you install this patch.
  3. Pick a "quiet" or low-traffic time  to install the patch on the Guardium system.
  4. Install patches in a top-down manner on all Guardium systems: start with the central manager, then aggregators, then the collectors.
For information about installing Guardium Data protection patches, see Installing patches in the Guardium documentation.
New support and functionality
Additional universal connector plug-ins 
Guardium Data Protection provides preinstalled plug-ins that you can use to create profiles by using the central manager workflow. The following new plug-ins are available on Guardium Data Protection version 12.1 with universal connector patch 12.0p5002 installed.
  • Azure MySQL over Event Hub
  • Cassandra Over Filebeat
  • Couchbase over Filebeat
  • CouchDB over Filebeat
  • GreenPlumDB Over Filebeat
  • MariaDB over Cloudwatch Logs
  • MariaDB over Filebeat
  • MySQL over Cloudwatch Logs
  • Mysql Percona Over Filebeat
  • Neodb Over Filebeat
  • OUA MultiTenant over JDBC connect
  • OUA MultiTenant over JDBC connect 2.0
  • Postgres over Cloudwatch Logs
  • Postgres Over Filebeat
For more information, see Configuring universal connectors by using a central manager in the product documentation. 
Enhancements
This patch includes the following enhancements.
Issue key Summary
GRD-94714 Refactor the validate function on the JDBC connector to run the query and test the connection
GRD-96792
Create a protobuf object for OUA audit logs to act an interface for the source connector and sink connector
GRD-96793 Change the Kafka Connect value.converter property with the protobuf converter
GRD-96794 Source connector - Copy implementation to universal connector bundle repository
GRD-96795 Source connector - Serialize to protobuf object when sending messages to topic 
GRD-96796 Sink connector - Add parser code to sink connector
GRD-96797 Sink connector - Deserialize the protobuf object when consuming messages from topic 
GRD-96798 Sink connector - During config creation, add the parameters such as topic, managed unit, and type
GRD-97107 Universal connector patch build script for Kafka connectors available in the universal connector bundle 
GRD-97577 Upgrade universal connector image to 1.6.7 in the universal connector bundle 
GRD-97578 Move the Guardium Data Protection packages from the public repository to the universal connector bundle
GRD-97579 Sink connector - Use the same consumer group ID for different connectors with the same profile 
GRD-97581 Sink connector - Use the datatype from commons enum 
Resolved issues
This patch resolves the following issues.
Patch
 Issue key Summary Known issue (APAR)
12.0p1006
See release note for patch 12.0p1006
12.0p5002
 GRD-89461 After updating the universal connector configuration, no universal connector traffic is captured on the Oracle database DT426533

 
Known issues
This patch includes the following known issues.
Issue key Summary
GRD-86940
Universal connector Kafka cluster nodes are not part of backup. 
Workaround: This will be fixed in a future patch.
GRD-98849
GRD-98851
 Upgrading from 12.0p105 (see release note) to 12.0p120 (see release note) and applying universal connector patch 12.0p5002 results in two different Oracle packages. "OUA over JDBC connect 2.0" profile is recommended. Do not use the "OUA over JDBC connect" profile.

Workaround: If Oracle data source profiles using the universal connector were installed on the system before the upgrade, uninstall the "OUA over JDBC connect" profiles, upload the same JDBC driver under a new name, and use this JAR to configure the "OUA over JDBC connect 2.0" new profile.
GRD-99009
GRD-100366
 Replacing dead Kafka broker node with healthy nodes has the following limitations:
  • Replacing the dead broker nodes works if more than 50% of the cluster nodes are still online. If more than 50% of the nodes are offline, a new Kafka cluster must be created.
  • Results in potential data loss.
  • Certain cruise control functionality may not be available.
  • Traffic for an existing topic is redistributed among currently online nodes. The new node does not handle traffic for existing topics. However, traffic for newly created topics will be evenly distributed across all available nodes.
GRD-100109

When viewing multiple predefined Kafka Cruise Control reports, maximizing one report minimizes the others and places them as tabs at the lower-right part of the window. However, these tabs are only visible when hovering the mouse.
GRD-100387
After applying patch 12.0p5002, when using version 12.1, the Oracle database plug-ins are not supported in Datasource Profile Management.
Workaround: Install 12.0p120 (see release note) and create the Kafka cluster after the installation to use data source profiles based on the Kafka cluster.
GRD-100601
 In case of a central manager failover, if a connector was previously failing, the system might not heal itself, resulting in incomplete or missing traffic capture across deployed managed units.
GRD-100746
 If the unified connector profile is installed on X collectors, and all of them remain unavailable for more than 2 hours, data loss may occur. 
GRD-100866
GRD-101053
 If 1,500 or more data sources profiles are installed on a central manager, loading the universal connector pages might delay.
GRD-100934
The recommended disk size of kafka-node unit is 1TB. Disk size below 1TB might result in the disk becoming full, causing the Kafka cluster to fail.
GRD-101420 For "OUA over JDBC connect 2.0", one Kafka cluster can handle up to 1,250 data sources profiles.
GRD-101478
Unable to create Kafka cluster by using the grdapi in Guardium version 12.1 with patch 12.0p120 (see release note) installed.
Workaround: Create the Kafka cluster by using the UI. For more information, see Creating Kafka clusters.
GRD-101566
Unable to use ojdbc8.jar file for bulk profile upload flow for "OUA over JDBC connect 2.0" and "OUA MultiTenant over JDBC connect 2.0" profiles. 
Workaround: To use the bulk upload feature, upload the ojdbc8.jar file individually with a unique name for the first data source profile of “OUA MultiTenant over JDBC connect 2.0” or “OUA over JDBC connect 2.0".
GRD-101762
In Guardium version 12.0p115 (see release note) with universal connector patch 12.0p1006 (see release note) installed, if patch 12.0p120 (see release note) is applied before patch 12.0p5002, then the profile creation of "OUA over JDBC connect 2.0" fails with an error.
Workaround: In Guardium version 12.0p115 with universal connector patch 12.0p1006 installed, first apply patch 12.0p5002 and then apply patch 12.0p120.

[{"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":"a8m3p000000PCTuAAO","label":"Platform\/Installation\/Deployment"},{"code":"a8m3p0000006xcfAAA","label":"UNIVERSAL CONNECTOR"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0.0;12.1.0"}]

Document Information

Modified date:
27 July 2025

UID

ibm17232496

Page Feedback