Database ingestion and replication incremental load and combined load jobs that have a Db2 for i source might fail repeatedly with cache container errors after you add a table for CDC processing, even if you resume or redeploy the job.

(October 2025)

Database ingestion and replication jobs that have a Db2 for i source might fail when generated key values sent to the cloud cache contain special characters.

(October 2025)

Database ingestion and replication jobs that have a Db2 for i source might have degraded performance caused by a large workload on non-transactional Units of Work (UOW).

(October 2025)

Database ingestion and replication incremental load and combined load jobs that have a Db2 for z/OS source might encounter degraded performance during CDC processing because extraneous processing that occurs on every stored procedure call.

(October 2025)

When database ingestion and replication incremental load or combined load jobs that have a Db2 for i source are restarted, a different sequence token might be generated for the same record, which can cause the job to write the record twice to the target.

(October 2025)

Database ingestion and replication incremental load and combined load jobs that have a Db2 for z/OS source might fail with the following error after a Db2 catalog entry that has no table objects is changed, for example, an index update in the SYSINDEXES catalog:

In this case, the catalog entry should be ignored so that the job can continue processing.

(October 2025)

If database ingestion and replication jobs read data from a Db2 for i source physical file that’s defined in DDS with a unique index but no primary key, the unique index won’t be used when generating the corresponding target object. After this fix, if no primary key is available, unique indexes are fetched from the SYSPARTITIONINDEXES view and used to update the schema used for target generation.

(May 2025)

For database ingestion and replication jobs that have a Db2 for i source, restart advance might not occur.

(May 2025)