Issue | Description |
|---|---|
DBMI-27223 | Adding the customPrimaryKeys source custom property to an existing incremental load or combined initial and incremental load task might result in a primary key change not allowed error. Following a resync, new DML changes are not replicated to the target, and a restart of the task shows the primary key change not allowed error for the resynced table. |
DBMI-24943, DBMI-27151 | When communication between the source CDC capture process and Data Ingestion and Replication fails, the monitoring interface still shows the job status as Up and Running although no data is being processed. |
Issue | Description |
|---|---|
DBMI-25249 | If you resume database ingestion and replication apply jobs that are part of a CDC staging group after they’ve stopped, the resume attempt initially fails. If you manually retry the resume operation multiple times, the apply jobs eventually resume processing. The problem occurs because of unnecessary scanning for the latest schema information in the schema history table. |
DBMI-25161 | Database ingestion and replication combined load jobs might fail with a java.lang.NullPointerException error during backlog processing if the TABLE_STATE_CHANGE marker is processed and the unload phase of the job runs on a Secure Agent different from the one that the job runs on. |
DBMI-24759 | If database ingestion and replication incremental load or combined load jobs that have a Db2 for z/OS source encounter a slight latency in reading source log data from near end-of-log (EOL), some source data might not be applied to the target. This data loss occurs in Db2 for z/OS data-sharing environments |