What's new and changed in Data Replication

Data Replication updates 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.

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.

Installing or upgrading Data Replication

Ready to install or upgrade Data Replication?

To install Data Replication along with the other IBM® Software Hub services, see Installing IBM Software Hub.
To upgrade Data Replication along with the other IBM Software Hub services, see Upgrading IBM Software Hub.
To install or upgrade Data Replication independently, see Data Replication.
Remember: All of the IBM Software Hub components associated with an instance of IBM Software Hub must be installed at the same version.

IBM Software Hub Version 5.2.2

A new version of Data Replication was released in October 2025 with IBM Software Hub 5.2.2.

Operand version: 5.2.2

This release includes the following changes:

New features

This release of Data Replication includes the following features:

Force stop replication jobs from the UI: You can now forcefully stop replication jobs that are stuck in the "Stopping" state. Jobs stuck in this transitional state might block new replication jobs. The force stop capability cleans up replication-related system resources.

Updates

The following updates were introduced in this release:

Encrypt IBM Data Replication Access Server connections with TLS: You can configure the IBM Data Replication Access Server to use TLS to encrypt connections to the remote data stores.
Use version 12.1 of the IBM Db2 Database as a source database: IBM Db2 Database version 12.1 is now supported as a source data store with the Data Replication service.
Set an aggregation buffer size limit to replicate large files to an IBM watsonx.data™ target datastore: Use the net effect aggregation buffer size setting to configure how much memory (in megabytes) your replication instance uses to replicate data to a watsonx.data target datastore. Use a buffer to manage changes to large files in the source datastore and reliably replicate operations that simultaneously add and delete data.

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.

Security issues fixed in this release

The following security issues were fixed in this release:

CVE-2025-5914, CVE-2025-6395, CVE-2025-8058, CVE-2025-8194, CVE-2025-8941, CVE-2025-21962, CVE-2025-30749, CVE-2025-30754, CVE-2025-32414, CVE-2025-32415, CVE-2025-32988, CVE-2025-32989, CVE-2025-32990, CVE-2025-37914, CVE-2025-38350, CVE-2025-38417, CVE-2025-50059, CVE-2025-50106, CVE-2025-58058, CVE-2025-58754

CVE-2024-31076, CVE-2024-36922, CVE-2024-36956, CVE-2024-36977, CVE-2024-42305, CVE-2024-43820, CVE-2024-43826

CVE-2023-53253, CVE-2023-53296, CVE-2023-53297, CVE-2023-53306, CVE-2023-53366, CVE-2023-53392, CVE-2023-53393, CVE-2023-53421, CVE-2023-53442, CVE-2023-53444

CVE-2022-29458, CVE-2022-50327, CVE-2022-50339, CVE-2022-50345, CVE-2022-50350, CVE-2022-50369, CVE-2022-50374, CVE-2022-50396, CVE-2022-50397, CVE-2022-50408, CVE-2022-50410

CVE-2021-47239, CVE-2021-47251, CVE-2021-47457, CVE-2021-47579

IBM Software Hub Version 5.2.1

A new version of Data Replication was released in August 2025 with IBM Software Hub 5.2.1.

Operand version: 5.2.1

This release includes the following changes:

Updates

The following updates were introduced in this release:

Replicating data to an IBM watsonx.data target database with the Change Log business goal creates additional metadata tables: When you replicate data to IBM watsonx.data with the Change Log business goal, the CHANGE_LOG_TXID_TO_COMMIT_TIMESTAMP and CHANGE_LOG_DDL_TYPE_TO_DESCRIPTION tables are created. In addition, the CHANGE_LOG_TXID_TO_COMMIT_TIMESTAMP is now created for each replication run instead of one instance of the table being shared across multiple replication instances.
Use new parameters to set up Oracle as a source database: When you replicate data from an Oracle database, you can now set the Replication heartbeat interval and Replication report no-activity threshold parameters to monitor the status of the data captured from the source database.

Issues fixed in this release

The following issues were fixed in this release:

New tables created without the CHANGE DATA CAPTURE flag enabled are not detected when the replication job is in the Running state

Issue: When replication is running and a new table is created without the CHANGE DATA CAPTURE flag, the table is not replicated, even if the flag is later enabled using an ALTER TABLE statement.
Resolution: The issue is now fixed.

Replication fails with OutOfMemoryError

Issue: Replication fails with OutOfMemoryError and remains in Running state without replicating any data.
Resolution: The issue is now fixed.

Timestamp column with default value fails to replicate to the target data store

Issue: When you run a data replication job with the Copy business goal setting, the job fails to replicate timestamp columns that contain a default value such as the current time value.
Resolution: The issue is now fixed.

Replication fails when creating PostgreSQL tables with columns containing double precision and time zone data types

Issue: When you try to replicate data from a PostgreSQL database, tables that contain double precision and time zone data types fail to replicate to the target database.
Resolution: The issue is now fixed.

Replication fails when updating Oracle tables with columns containing timestamps

Issue: When you try to update tables in an Oracle database with the ALTER TABLE ADD COLUMN option, the operation fails.
Resolution: The issue is now fixed.

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.

Security issues fixed in this release

The following security issues were fixed in this release:

CVE-2025-0938, CVE-2025-21759, CVE-2025-21887, CVE-2025-21919, CVE-2025-21929, CVE-2025-21961, CVE-2025-21963, CVE-2025-22085, CVE-2025-22126, CVE-2025-22868, CVE-2025-22871, CVE-2025-23150, CVE-2025-24528, CVE-2025-24928, CVE-2025-25724, CVE-2025-27817, CVE-2025-3576, CVE-2025-37738, CVE-2025-37750, CVE-2025-37799, CVE-2025-37943, CVE-2025-38089, CVE-2025-38395, CVE-2025-4138, CVE-2025-4330, CVE-2025-4373, CVE-2025-4435, CVE-2025-4517, CVE-2025-4673, CVE-2025-46762, CVE-2025-4802, CVE-2025-48060, CVE-2025-48734, CVE-2025-49794, CVE-2025-49796, CVE-2025-50181, CVE-2025-5702, CVE-2025-6020, CVE-2025-6021, CVE-2025-6965, CVE-2025-7339, CVE-2025-7425, CVE-2025-7783

CVE-2024-10963, CVE-2024-12133, CVE-2024-12243, CVE-2024-12718, CVE-2024-23337, CVE-2024-31141, CVE-2024-47081, CVE-2024-52533, CVE-2024-56171

CVE-2023-53042, CVE-2023-53056, CVE-2023-53095, CVE-2023-53100, CVE-2023-53112

CVE-2022-49043, CVE-2022-49846, CVE-2022-49958, CVE-2022-49959, CVE-2022-49966, CVE-2022-49974, CVE-2022-49981, CVE-2022-49986, CVE-2022-50001, CVE-2022-50003, CVE-2022-50007, CVE-2022-50015, CVE-2022-50019, CVE-2022-50027, CVE-2022-50033, CVE-2022-50034, CVE-2022-50041, CVE-2022-50042, CVE-2022-50046, CVE-2022-50076, CVE-2022-50086, CVE-2022-50112, CVE-2022-50120, CVE-2022-50123, CVE-2022-50124, CVE-2022-50133, CVE-2022-50138, CVE-2022-50157, CVE-2022-50181, CVE-2022-50187, CVE-2022-50194, CVE-2022-50196

IBM Software Hub Version 5.2.0

A new version of Data Replication was released in June 2025 with IBM Software Hub 5.2.0.

Operand version: 5.2.0

This release includes the following changes:

Updates

The following updates were introduced in this release:

Use IBM watsonx.data as a target data store for replicating data with a change log

You can now use the Data Replication service to replicate data to IBM watsonx.data after you set up a replication pipeline that uses the Change Log business goal setting to track modifications to the source database.

Replicate more data types from an Oracle database to a target database

You can now replicate the following additional data types from an Oracle database:

INTERVAL DAY TO SECOND
INTERVAL YEAR TO MONTH
BLOB
CLOB
NCLOB
UROWID
XMLTYPE

Use IBM Db2 pureScale® when you replicate data from a Db2 database

You can now scale your Db2 database environment by using IBM Db2 pureScale with the Data Replication service.

Replicate data with IBM Db2 Database connections that use self-signed certificates

You can now use SSL with self-signed certificates to encrypt connections from a Db2 database when you can now replicate data from the database to a target datastore.

FIPS 140-3 compliant

Data Replication service is now FIPS 140-3 compliant for some source and target datastores. For details, see Services that support FIPS.

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.

Security issues fixed in this release

The following security issues were fixed in this release:

CVE-2025-0395, CVE-2025-1272, CVE-2025-5889, CVE-2025-21587, CVE-2025-21669, CVE-2025-21756, CVE-2025-21927, CVE-2025-22871, CVE-2025-22872, CVE-2025-27817, CVE-2025-30065, CVE-2025-30698, CVE-2025-37749

CVE-2024-7592, CVE-2024-8176, CVE-2024-43855, CVE-2024-47141, CVE-2024-53105, CVE-2024-53142, CVE-2024-53150, CVE-2024-53156, CVE-2024-53160, CVE-2024-53208, CVE-2024-53213, CVE-2024-53222, CVE-2024-53237, CVE-2024-54680, CVE-2024-56544, CVE-2024-56551, CVE-2024-56601, CVE-2024-56611, CVE-2024-56623, CVE-2024-56631, CVE-2024-56653, CVE-2024-56663, CVE-2024-57894, CVE-2024-58009

CVE-2023-4752, CVE-2023-52917