Issue | Description |
|---|---|
DBMI-22299 | If you define a CDC staging group that includes multiple database ingestion and replication incremental load or combined load apply tasks and you add a source table to one of the apply tasks after its associated job is running and then redeploy that job, the group job also redeploys. During the group job redeployment, the other apply jobs in the group stop. |
DBMI-22449 | If you set the target custom property writerRowSequenceMergeApplyLimit to a value greater than the default value of 13 for a database ingestion and replication job, the job fails with the following exception because some merge apply code is trying to use the default value rather than the specified value: Exception handled: 'Numeric value '' is not recognized'. With error code 100038. If you Resume the job, it resumes normal processing. |
DBMI-22174 | When you run a database ingestion and replication job as part of the CDC Staging task, the job log is not showing the information which file is being processed. |
DBMI-21955 | When you run a database ingestion and replication job as part of the CDC Staging task and use the Audit or Soft Deletes apply mode, the metadata columns associated with the apply mode are not populated with any data. |
DBMI-21522 | In the new configuration wizard, if you add a CDC staging group to a database ingestion and replication task and then deploy and run the task, you cannot remove the staging group from the task later. |
DBMI-21411 | If you undeploy a deployed database ingestion and replication job that uses the Audit or Soft Deletes apply mode and then change the apply mode to Standard and redeploy the job, the metadata columns created for the Audit or Soft Deletes apply mode are inappropriately retained in the configuration that uses the Standard apply mode. |
Issue | Description |
|---|---|
DBMI-22285 | After you run a database ingestion and replication task that is part of a CDC staging group, if you add another combined load task to the staging group and deploy it and then redeploy its job, the first job might fail with the following error: Cannot invoke "java.util.concurrent.ThreadPoolExecutor.awaitTermination(long, java.util.concurrent.TimeUnit)" The problem occurs when the first job is processing a large amount of data. Note: The CDC staging group feature is available in the new task configuration wizard only. |
DBMI-22172 | If database ingestion and replication combined load jobs in a CDC staging group have not yet written newly captured change data to the staging area, backlog apply processing of change data might be incomplete, causing duplicate inserts on the target. |
DBMI-21877 | A database ingestion and replication combined initial and incremental load job that uses the Audit mode might generate before-image records when there is CDC data during the backlog phase of the task, even though the Add Before Images option is not selected in the advanced properties on the Target page of the task wizard.The job might fail with the following error: The given row cannot be converted to the internal format due to invalid value |
DBMI-21521 | If you define a CDC staging group in the new task configuration wizard, the CDC staging task can't run on a Windows agent. |
DBMI-21485 | If you define a CDC staging task in the new task configuration wizard and then try to export the task, the export operation fails. |
DBMI-21427 | In Operational Insights, if you select CDC Staging as the Job Type filter, no information is displayed, even if CDC Staging Tasks exist. The page is blank. |
Issue | Description |
|---|---|
DBMI-21703 | Database ingestion and replication incremental load jobs that have a Db2 for i source might fail if there are two journal receivers in the Attached state in the journal receiver list or if there are no Attached journal receivers in the list. One of the following error messages might be issued: [CDCPUB_10066] TRACE: [IBMiLogCollector getLogMinMax(), Receiver <OMS85N9515> is not the last Journal Receiver in the list. No query needed.]. [CDCPUB_10066] TRACE: [PwxCDCReaderRunHandler encountered error :IBMiLogCollector newEndOfLogChecks() exception, IBMiLogCollector getJournalReceiverInfoByOption(), did not find journal information for receiver name .. Caused by: IBMiLogCollector getJournalReceiverInfoByOption(), did not find journal information for receiver name .]. |
DBMI-21124 | After you upgrade to new release, if the Secure Agent is running multiple database ingestion and replication jobs, a deadlock can occur. In this case, the jobs appear to be running for hours but without moving any data. |