Fixed issues

After the July 2025 release, application and database ingestion and replication jobs with Kafka targets might fail with the following error, even after they’re Undeployed and Deployed again:

The problem occurs because the default consumer group name of infaGroup that Database Ingestion and Replication uses for high availability was not authorized.

After the July 2025 release, database ingestion and replication jobs and application ingestion and replication jobs that use the combined load type and that have a data lake target ,such as Microsoft Azure Data Lake Store, use asynchronous uploads of output files for the unload phase by default. If the Use Cycle Partitioning for Data Directory option is selected for these jobs, the output files from the unload phase are incorrectly stored under the data directory instead of under a timestamp subdirectory.

Database ingestion and replication jobs and application ingestion and replication jobs might encounter the following error:

In rare cases, the DBMI Agent service does not shut down cleanly after prolonged failures of communication with the Informatica cloud, which causes interruptions to the agent restart process and an eventual ERROR state.

When you create a source table selection rule in the new task configuration wizard, if you define an Exclude rule that excludes a primary key column, the column is deselected.The primary key columns should remain selected for proper CDC processing.

When an application ingestion and replication job or database ingestion and replication job has persistent storage enabled, the following error can be reported if change stream corruption occurs:

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.