Fixed issues

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:

If you previously deployed a database ingestion and replication job in the Audit or Soft Deletes apply mode, undeployed the job and then redeployed it with a change to the Standard apply more, the metadata columns created for the Audit or Soft Deletes apply mode are retained in the source tables. The target tables no longer receive changes for these columns and the job might fail.

If a database ingestion and replication job includes a source table without a primary key and you set the custom property readerUseUniqueIndexAsPrimaryKey set to true on the Source page of the task wizard, the job might erroneously consider all indexes for primary key calculation, instead of unique indexes only.

The Secure Agent Database Ingestion service fails to delete the temporary IOTest.dat file from /infaapp/iics/infaagent/apps/Database_Ingestion/data/tasks.

In the Data Ingestion and Replication Command-Line Interface (CLI), the resumeWithOptions resync and resyncSubtask commands with the resync, resyncRefresh, or resyncRetain option do not print validation messages to indicate the commands successfully triggered resync processing for the job or table subtask. With this fix, appropriate validation messages are issued to indicate that the job or table is being resynchronized.

In the monitoring job details for database ingestion and replication combined initial and incremental load jobs, the Object Detail section shows an Unload Count of records for the initial load phase that is less than the count of records read from the source table. The discrepancy occurs because the Unload Count was obtained before all writes to the target had completed.

If a database ingestion and replication incremental load or combined load job fails before checkpoint information is written to the target, when you resume the job, the job might resume CDC processing from a later point in time, instead of from the same point as used for the initial startup. In this case, some source operations might be skipped during capture processing.

If you select the advanced Add Last Replicated Time property on the Target page of the task wizard and save task and then later clear the check box and save the task again, when you return to the task wizard, the check box is still selected. However, if you open the task in view mode, the property is disabled. In this case, the database ingestion and replication job does not add the last replicated time metadata column on the target, which appears to conflict with the wizard setting.

Database ingestion and replication jobs that have a Snowflake target and use the Superpipe feature to stream change data to target tables might fail with the following error if mixed-case and lowercase column identifiers are quoted and if the QUOTED_IDENTIFIERS_IGNORE_CASE=true parameter is set in the Additional JDBC URL Parameters field of the connection properties:

In the Data Ingestion and Replication Command-Line Interface (CLI), if you issue the job status command without the optional -f option, the command fails with the following error:

The failure occurs because of date-time format discrepancies that are encountered when fetching the job's start time.

Redeployed database ingestion and replication combined load jobs that have an Oracle 11g source might fail with the following error when querying redo logs for start information: