Issue | Description |
|---|---|
DBMI-25346 | Database ingestion and replication incremental load and combined load jobs that have an Oracle source and use the BFILE log access method might report stale buffer files when the files are in an Oracle server file system on Linux. If the default settings for the status check interval and archive wait time are too high, this cache storage problem might not be detected or detection might be delayed. |
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 |