What's new and changed in Data Gate
The Data Gate release and subsequent refreshes can include new features and fixes. Releases are listed in reverse chronological order so that the latest release is at the beginning of the topic. Only the refreshes that contain updates for Data Gate are shown.
You can see a list of the new features for the platform and all of the services at What's new in IBM Software Hub.
IBM Cloud Pak for Data Version 5.4.0
A new version of Data Gate was released in June 2026.
This release includes the following changes:
- New features
-
This release of Data Gate includes the following features:
- Data Gate supports TLS 1.3
- Data Gate now supports TLS 1.3 for connections between Db2 for z/OS and Data Gate, which eliminates less safe legacy cryptographic algorithms and reduces handshake overhead to a single round trip. Every session benefits from forward secrecy by default, which satisfies compliance requirements that mandate newer TLS versions. Customers can choose between TLS 1.2 and TLS 1.3 by configuring their AT-TLS rules accordingly. See Configuring network access between Data Gate and IBM Z.
- New REST APIs for programmatic management of replicated tables
- A new set of REST APIs provides an initial set of operations for retrieving information about and working with replicated tables, enabling automation through CI/CD pipelines, infrastructure-as-code, or custom tooling without touching the UI. See Managing Data Gate tables.
- Monitoring via a Prometheus-compatible metrics endpoint
- Data Gate exposes a Prometheus scrape endpoint, making key metrics — synchronization latency and throughput — available to any compatible monitoring stack. Teams using Grafana can plug straight in for dashboards and alerting. This feature replaces the deprecated monitoring UI. See Monitoring a Data Gate instance.
- Configurable database name for remote Db2 target databases
- Previously, Data Gate enforced a 1:1 relationship between a Data Gate instance and its target database, with the target database name hardcoded as BLUDB across multiple components. Starting in this release, the target database name is configurable for remote Db2 and Db2 Warehouse scenarios. You can now specify the target database name when it differs from BLUDB. This also enables the possibility of reusing an existing Db2 instance — including instances with multiple databases — as the target for more than one Data Gate instance. See Connecting to a remote Db2 instance
- Query acceleration and storage saver for remote Db2 target databases
- Data Gate can be connected to a remote Db2 (transactional) or remote Db2 Warehouse (analytic) instance. For analytic targets, Data Gate supports a special mode that enables additional use cases from the Db2 for z/OS source side. Starting in this release, query acceleration mode is now supported for remote Db2 targets. Query acceleration mode allows you to execute queries via Db2 for z/OS on Data Gate tables, and to archive table partitions to move them to Data Gate (storage saver). This option can be selected at instance provisioning time. Extending support to remote Db2 targets brings feature parity with other target configurations. See these links for more information: Data Gate query acceleration and Data Gate storage saver.
- Helm-based management of Data Gate instances without Operator Lifecycle Manager
- Data Gate instances can now be managed via Helm charts, which unlocks GitOps-based instance management workflows and provides a better tracking of deployment phases via improved progress messages.
- Updates
- The following updates were introduced in this release:
- Improved remote Db2 functions
- Remote Db2 function support has been extended and hardened, covering a broader range of function types with improved reliability and error handling.
- Improved certificate-based authentication for connections to Db2 for z/OS
- Certificate-based authentication for connections from Data Gate to the Db2 for z/OS source database is now more robust. It can be configured without requiring a restart of the Data Gate pod, and error reporting on authentication failures has been improved.
- Improved OpenShift permission management for role-based access controls
- Security has been improved by minimizing the cluster-level permissions that need to be granted to the Data Gate service.
- Issues fixed in this release
- The following issues were fixed in this release:
- Fixed an issue where Data Gate "tries" to manage user IDs in the Db2 target database.
- Fixed an issue with broken permissions of Data Gate instance management scripts after an upgrade.
- Fixed the error message for invalid certificates that is passed to source connection management APIs.
- Fixed an issue where Data Gate traces were missing in diagnostics collections.
- Customer-reported issues fixed in this release
- For a list of customer-reported issues that were fixed in this release, see the Fix List for IBM Cloud Pak for Data on the IBM support website.
- Deprecated features
- The following features were deprecated in this release:
- Monitoring a Data Gate instance
- The monitoring dashboard previously available for Data Gate instances is deprecated. Prometheus and Grafana are now the recommended tools for monitoring Data Gate instances.