Fixed issues

Application ingestion and replication jobs and database ingestion and replication jobs that have the DBMI_CDC_READER_CFG_OPTIONS environmental variable set might fail with the following message:

For application ingestion and replication jobs and database ingestion and replication jobs that are configured to check if the count of DML records from the source has increased since the last check, the DML check might not be performed.

If you add multiple custom properties or table renaming rules when configuring an application ingestion and replication task or database ingestion and replication task in the latest task wizard, the Back, Next, Save, and Deploy buttons are no longer displayed.

If you set the writerTruncateTargetOnStartup custom property to false for an application ingestion and replication job or database ingestion and replication job that uses the combined load type and Audit apply mode, the job might truncate old audit data in the target table when it runs the second time after redeployment.

When running an application ingestion and replication or a database ingestion and replication job that has the persistent storage enabled, the task container might log a purgeLogRequest message for every reader persistence row, which might result in excessive usage of disk space.

When running an application ingestion and replication or a database ingestion and replication job that have a missing PWX Service logs subdirectory, the logs might not be cleared according to the specified log retention period.

After the February 2025 upgrade, the Secure Agent Database Ingestion service might generate an excessive amount of log files at /app/infaagent/apps/Database_Ingestion/logs/services/task_container/Default, which can potentially consume all storage on disk.

If you configured rules to filter source data rows when defining an application or database ingestion and replication task in the new configuration wizard, you can’t edit the rules after deploying the task unless you first undeploy the job and then deploy the task again. With this fix, you can now edit row-level filtering rules in the task, without first undeploying the job, and then Redeploy the job for the updated rules to take effect.

When you stop an application ingestion and replication and database ingestion and replication job, the request to stop the job might fail to be delivered, but the DBMI Agent might treat the job as successfully stopped.

If the Secure Agent fails to get status information for the Database Ingestion service because of an OutOfMemory error, the agent falsely assumes that the Database Ingestion service is down and displays an error in the Runtime Environments page. The Database Ingestion service is actually in the Up and Running state and continues to run the jobs, although any user actions on the jobs fail.

For an application ingestion and replication and database ingestion and replicationjobs, when you use the Audit or Soft Deletes apply mode and define rules to specify a subset of source tables to replicate, the Consistency Checker might drop tables at the target side because of a mismatch in the target column count.

For an application ingestion and replication or database ingestion and replication initial load job that fails with the target custom property writerSqlUnloadAsyncLoading set to true, the monitoring interface might incorrectly display the status of Completed.

Unload processing in application or database ingestion and replication tasks that use the initial load or combined initial and incremental load type might take a long time to complete.

When application ingestion and replication or database ingestion and replication jobs are terminated, the task units where the Secure Agent is running might not be released, which causes the number of available task units to remain static.

A duplicate instance of an application ingestion and replication job or a database ingestion and replication job might run in another agent when the original Secure Agent running the job expires and restarts the job.