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.
IBM Cloud Pak for Data Version 5.2.2
A new version of Data Replication was released in October 2025.
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.
For details, see Managing replication jobs.
- 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.
For details, see IBM Data Replication Access Server connection.
- 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.
IBM Cloud Pak for Data Version 5.2.1
A new version of Data Replication was released in August 2025.
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_TIMESTAMPandCHANGE_LOG_DDL_TYPE_TO_DESCRIPTIONtables are created. In addition, theCHANGE_LOG_TXID_TO_COMMIT_TIMESTAMPis now created for each replication run instead of one instance of the table being shared across multiple replication instances.For details, see Frequently asked questions for the Change Log business goal.
- 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.
For details, see Replicating Oracle data.
- Issues fixed in this release
- The following issues were fixed in this release:
- New tables created without the
CHANGE DATA CAPTUREflag enabled are not detected when the replication job is in theRunningstate -
- Issue: When replication is running and a new table is created without the
CHANGE DATA CAPTUREflag, the table is not replicated, even if the flag is later enabled using anALTER TABLEstatement. - Resolution: The issue is now fixed.
- Issue: When replication is running and a new table is created without the
- Replication fails with
OutOfMemoryError -
- Issue: Replication fails with
OutOfMemoryErrorand remains inRunningstate without replicating any data. - Resolution: The issue is now fixed.
- Issue: Replication fails with
- 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 COLUMNoption, the operation fails. - Resolution: The issue is now fixed.
- Issue: When you try to update tables in an Oracle database with the
- New tables created without the
- 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.
IBM Cloud Pak for Data Version 5.2.0
A new version of Data Replication was released in June 2025.
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.
For details, see Choosing a business goal for the replication asset.
- 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
For details, see Supported Oracle data types
- 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.
For details, see Replicating Db2 data
- 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.
For details, see Replicating Db2 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.