Issue | Description |
|---|---|
DBMI-28703 | You do not have the option to configure task-level Java Virtual Memory (JVM) for tasks running in serverless runtime environments. |
DBMI-28508 | For application ingestion and replication and database ingestion and replication combined load jobs, markers intended for initial load and backlog processing might incorrectly trigger the incremental load processing with no recovery checkpoints written, which might lead to duplicate data on restart. |
DBMI-28447 | Data Ingestion and Replication components contain outdated jose4j release 0.9.4 inherited from a third party driver. |
DBMI-28238 | When an application ingestion and replication job or a database ingestion and replication job restarts after a failure, data for a table that was already sent to the target might be resent while recovering data for other tables not yet sent to the target. |
DBMI-27833 | For organizations that use the shared secure agent group with multiple agents from parent organization, same unload tasks within a database ingestion and replication or application ingestion and replication might be are assigned to more than one agent, resulting in duplicate unloads for the same table. |
DBMI-27520 | Application ingestion and replication combined load jobs and database ingestion and replication combined load jobs that use custom properties related to the load transition processing might ignore those custom properties and instead apply only the default values. The following error might be issued: Remote task submission failed due to invalid ReservationId |
DBMI-27223 | Adding the customPrimaryKeys source custom property to an existing incremental load or combined initial and incremental load task might result in a primary key change not allowed error. Following a resync, new DML changes are not replicated to the target, and a restart of the task shows the primary key change not allowed error for the resynced table. |
DBMI-26176 | Data Ingestion and Replication components contain vulnerable Simba JDBC driver. |
Issue | Description |
|---|---|
DBMI-25680 | 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: Error :Not authorized to access group: infaGroup The problem occurs because the default consumer group name of infaGroup that Database Ingestion and Replication uses for high availability was not authorized. |
DBMI-25542 | 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. |
DBMI-25460 | Database ingestion and replication jobs and application ingestion and replication jobs might encounter the following error: Purging of illegal message failed for topic CONTAINER_SERVICE-task-status-topic |
DBMI-25425 | 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. |
DBMI-19633 | 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. |
Issue | Description |
|---|---|
DBMI-28633 | When you try to stop a database or application ingestion and replication job that is already in a stopped state because of the API endpoint POST request /dbmi/public/api/v2/job/stop, the API incorrectly returns a 404 status code with the error message "JOB_IS_NOT_ACTIVE". Instead, the API should return a 409 status code to indicate a conflict. (April 2026) |
DBMI-26372 | When you view details of an application ingestion and replication job or a database ingestion and replication job from Monitor, the overall job status might be missing from the job details page. (October 2025) |
Issue | Description |
|---|---|
DBMI-25116 | For application ingestion and replication jobs and database ingestion and replication jobs that have an Amazon Redshift target, if a source column of a string datatype contains NULL data, the values are written as empty strings ("") to the target. (October 2025) |
Issue | Description |
|---|---|
DBMI-26804 | Application ingestion and replication jobs and database ingestion and replication jobs that have an Amazon S3 target might fail if the AWS region of the S3 bucket is AWS GovCloud (US-West). The following error message is issued: Cannot create enum from region description AWS GovCloud (US-West) value (April 2026) |
Issue | Description |
|---|---|
DBMI-28330 | For application ingestion and replication jobs and database ingestion and replication jobs that have a Databricks target and use volume staging, when the initial file upload attempt fails because of network connectivity issues and leaves partially written files, the subsequent retry attempts might fail. The failure occurs because the retry logic does not overwrite existing partial files by default, resulting in an error. The error indicates that the file already exists in staging and overwriting it is not enabled. (April 2026) |
DBMI-27152 | For application ingestion and replication tasks and database ingestion and replication tasks that have a Databricks target, empty strings ("") in a source string column are incorrectly replicated as NULL to the Databricks target. (April 2026) |
DBMI-26154 | Application ingestion and replication jobs and database ingestion and replication jobs that have a Databricks target might fail during the COPY INTO operation if a source table begins with a special character. (April 2026) |
DBMI-22028 | Application ingestion and replication jobs and database ingestion and replication jobs that have a Databricks Unity Catalog target might fail with an error related to invalid Min Workers or Max Workers values. The job directly parses the values without handling invalid or malformed input. (April 2026) |
Issue | Description |
|---|---|
DBMI-26101,DBMI-26373 | For application ingestion and replication or a database ingestion and replication tasks that use the Databricks target, the volume generated automatically as the staging environment is not deleted along with the "temp_jobid" directory when the task is in stopped and failed state. (October 2025) |
Issue | Description |
|---|---|
DBMI-24787 | If you configured a proxy server but then tried to bypass it for Secure Agent communication with Google BigQuery targets by setting task_container.jvm.http.nonProxyHosts property at agent level, ingestion and replications jobs that have Google BigQuery targets might fail. The jobs fail because communication still goes through the proxy, and communications from the proxy are blocked a firewall. (October 2025) |
Issue | Description |
|---|---|
DBMI-25753 | For application ingestion and replication tasks and database ingestion and replication tasks that use a single topic for all writes to the Kafka target, the restart logic examines all Kafka topics instead of only the required topic, which might cause the task to fail if access to all topics is not allowed. (October 2025) |
Issue | Description |
|---|---|
DBMI-19405 | Tests of a Microsoft Azure Synapse Analytics Database Ingestion connection for an application ingestion and replication task or database ingestion and replication task fail with the following error if the user name specified in the connection properties includes a special character such as @ and the target database uses AAD authentication: Cannot instantiate datasource because of error: Failed to initialize pool: Cannot open server 'noconline.onmicrosoft.com' requested by the login. The login failed. ClientConnectionId: <identifier> This problem occurs when the Synapse Analytics connector package is missing some required .jar files. These .jar files have now been added in the connector package at package-AzureDWGen2MI.xxx\package\dw\thirdparty\informatica.azuredwgen2mi:
(April 2026) |
Issue | Description |
|---|---|
DBMI-25163 | For application ingestion and replication jobs and database ingestion and replication jobs that have a SQL Server target, if more than three DML operations are performed on primary key column values of the same row in a CDC cycle, the job might fail with a primary key constraint error. (October 2025) |
Issue | Description |
|---|---|
DBMI-28191 | For application ingestion and replication and database ingestion and replication jobs that have a Snowflake target and use the Superpipe option, when the job is restarted, the generated recovery table might contain duplicate entries which are not detected at startup. (April 2026) |
DBMI-26132 | Application ingestion and replication and database ingestion and replication combined load jobs might fail with the followng error: BacklogReader does not implement insertMarkerWithAnnotations() (October 2025) |
DBMI-26085 | If multiple application ingestion and replication tasks or database ingestion and replication tasks that have differently configured Snowflake target properties are deployed nearly simultaneously, the Data Ingestion and Replication writer might use the incorrect target properties from the other task. In this situation, the deployment might fail or unexpected behavior related to the target table definitions can occur. (October 2025) |
DBMI-25090 | After the May 2025 release, application or database ingestion and replication jobs that have a Snowflake Data Cloud target and use Authorization Code authorization might fail with the following error when the access token that's generated from user interface expires: :caused by: net.snowflake.client.jdbc.SnowflakeSQLLoggedException: JDBC driver internal error: Unsupported authenticator type: OAUTH The error occurs because of the JDBC driver upgrade in the May release. (October 2025) |