Release Notes for IDMC
- Release Notes for IDMC
- All Products
ASK INFAPreview
Please log in to access Ask INFA.
ASK INFAPreview
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 |
Issue | Description |
|---|---|
DBMI-24977 | A CDC Staging Task lags far behind in reading the latest change
data from the source because of pushback processing by the apply
jobs in the staging group. |
DBMI-24849 | After a Resync operation, database ingestion and replication
combined load jobs might report duplicate DML records on the
target. This problem occurs because the CDC Reader allows the
last DML record processed to be re-sent to the writer on
startup, after the writer has already consumed that record. |
DBMI-24565 | Database ingestion and replication combined load jobs that use the Audit apply mode and
include the INFA_OPERATION_SEQUENCE metadata column in the
target tables might generate an incorrect operation sequence
after transitioning to incremental load processing. |
Issue | Description |
|---|---|
DBMI-24167 | When you run a database ingestion and replication job as part of the CDC Staging Task,
the job might hang if a large amount of obsolete CDC data exists
in the CDC staging group's staging storage. |
DBMI-23956 | When you run a database ingestion and replication job as part of the CDC Staging Task,
the job might fail with the following error message:
|
DBMI-23954 | After a database ingestion and replication job is undeployed, the
intermediate_storage_backup directory under the Database
Ingestion agent service at
…/informatica/SA/apps/Database_Ingestion/data/services/task_container/Default/intermediate_storage_backup/…
is not deleted and continues to consume disk space, even though
its files are marked as deleted. However, the main
intermediate_storage directory is deleted as expected. |
DBMI-23561 | Database ingestion and replication jobs that use Audit apply mode and include the
INFA_OPERATION_SEQUENCE metadata column in the target tables
might generate a non-sequential value in the metadata
column. |
DBMI-23357 | On the My Jobs page and on the Monitor > Running Jobs and All Jobs
pages, the Undeploy command is available in the Actions menu for CDC
Staging Tasks but isn't ready yet for use. If you try to use it, an
error message warns that it's unsupported. |
