New features and enhancements

The October 2026 release of Data Ingestion and Replication includes the following new features that are common to multiple types of ingestion and replication tasks.

Java Runtime Environment 17 requirement for Data Ingestion and Replication Command-Line Interface

The Data Ingestion and Replication Command-Line Interface (CLI) requires Java Runtime Environment (JRE) 17 or later version. If you run the CLI on an earlier JRE version, the CLI stops with a message indicating that JRE 17 or later is required.

REST API enhancements for creating tasks

The REST API request POST /dbmi/public/api/v2/task/create that creates an application ingestion and replication or database ingestion and replication task includes additional configuration options. The REST APIs now handle errors better and return clearer messages when a request fails.

The following list shows some of the new options you can configure through this API:

You can also enable automatic performance tuning in your request. The task automatically tunes initial load jobs and the initial phase of combined load jobs, so you don't need to adjust performance settings manually.

For special processing needs, you can set custom properties at the direction of Informatica Global Customer Support or a technical staff member.

For the full list of attributes that you can specify in your request, see Database Ingestion and Replication REST API Reference.

Connection list refresh in the task wizard

You can refresh the list of connections on the Source or Destination page of the task wizard. If you create a connection from the Administrator page while the task is open, refresh the connection list to select the new connection without closing or reopening the task.

Confirmation prompt when undeploying tasks

A confirmation dialog appears before you undeploy an application ingestion and replication, database ingestion and replication, or streaming ingestion and replication task.

You must confirm the action before the task is undeployed. This prompt prevents you from accidentally undeploying a running task when you click Undeploy.

Audit metadata columns for Microsoft Fabric OneLake targets

You can now configure audit metadata columns for tasks with a Microsoft Fabric OneLake target. This functionality is available for application ingestion and replication tasks that have a Salesforce source and database ingestion and replication tasks that have a MySQL, Oracle, and SQL Server source.

In Advanced Options under Advanced Target Properties, you can enable columns that track change-data metadata, such as operation type, operation sequence, and last replicated timestamp. To identify the source table or source schema for each replicated row, you can also enable the source table name and source schema name columns using target custom properties.

Schema drift options enabled for Microsoft Fabric OneLake targets

Automatic schema drift detection and handling is now available for Microsoft Fabric OneLake targets in incremental load and combined initial and incremental load application ingestion and replication jobs and database ingestion and replication jobs.

Schema drift occurs when you add, modify, drop, or rename columns in a source table.When defining a task, you can configure the types of source schema changes to propagate and how to handle them on the target. For example, you can configure schema drift options to ignore the changes, replicate the changes, or stop the job or a subtask when a schema change occurs. If you choose to stop the job, you can use the Resume With Options command to resume the job with an override schema drift option.

IAM Role ARN property available for Amazon S3 targets

You can now use the IAM Role ARN property in the Amazon S3 V2 target connection properties for application ingestion and replication tasks and database ingestion and replication tasks. Previously, this property did not apply to Data Ingestion and Replication tasks.

The IAM Role ARN property is used in the AssumeRole with EC2 role and AssumeRole with IAM user authentication types. In both types, the Secure Agent assumes the specified role through AWS Security Token Service and obtains temporary credentials automatically, so you don't need to store a long-lived access key or secret key in the connection. Cross-account Amazon S3 access is now possible without modifying the Secure Agent's own instance role.

Amazon Redshift JDBC driver upgrade

The Amazon Redshift JDBC driver has been upgraded from version 2.1.0.30 to 2.2.7 to address a security vulnerability that could allow unauthorized code execution under certain conditions. No configuration changes are required. Existing Amazon Redshift connections continue to work as before the upgrade.

Microsoft SQL Server JDBC driver upgrade

Data Ingestion and Replication now includes Microsoft SQL Server JDBC driver version 13.2.1 when you connect to Microsoft SQL Server sources and targets. This version replaces driver version 12.10.2, which reached end of life.

Secure Agent on Red Hat Enterprise Linux (RHEL) 10

You can now install the Secure Agent on RHEL 10 to handle your Data Ingestion and Replication tasks.

New Data Ingestion and Replication CLI options to override connection and runtime environment IDs

In the Data Ingestion and Replication Command-Line Interface (CLI) task create and task replace commands, you can now specify the source connection ID, target connection ID, and runtime environment ID as command-line arguments to override the values in the configuration file. This lets you reuse the same configuration file across organizations, such as when you promote a task configuration from a development environment to production. In the task replace command, you can also specify an argument to retain the connection and runtime environment IDs already stored in the repository.

The syntax for task create is:

task create --pathToConfig path_to_configuration_file [--taskName task_name][--taskLocation task_location][--taskType task_type][--deploy][--sourceConnectionId source_connection_id][--targetConnectionId target_connection_id][--runtimeEnvId runtime_environment_id]

The syntax for task replace is:

task replace --pathToConfig path_to_configuration_file [--taskName task_name][--taskLocation task_location][--deploy][--noprompt][--sourceConnectionId source_connection_id][--targetConnectionId target_connection_id][--runtimeEnvId runtime_environment_id][--retainExistingIds]

Job management from the task configuration page

You can now run, stop, abort, resume, redeploy, and undeploy application ingestion and replication jobs and database ingestion and replication jobs directly from the task configuration page. The Actions menu in the upper-right corner of the page displays options based on the current job status. You no longer need to navigate to the My Jobs page, Monitor, or Operational Insights to manage your jobs.

Serverless runtime environments extended to Cloud Data Lake targets

You can run application ingestion and replication and database ingestion and replication jobs on a serverless runtime environment hosted on Microsoft Azure with Cloud Data Lake targets such as Amazon S3, Google Cloud Storage, Microsoft Azure Data Lake Storage, Microsoft Fabric OneLake, and Oracle Cloud Object Storage targets.

Database Ingestion and Replication can now run incremental load and combined initial and incremental load jobs that use the Query-based CDC method to capture changes from an Oracle or SQL Server source and load to Cloud Data Lake targets using a serverless runtime environment.

Automatic agent switchover extended to Cloud Data Lake targets

Automatic switchover to another Secure Agent in a Secure Agent group is enabled by default for new application ingestion and replication jobs and database ingestion and replication jobs with Cloud Data Lake targets, such as Amazon S3, Google Cloud Storage, Microsoft Azure Data Lake Storage, Microsoft Fabric OneLake, and Oracle Cloud Object Storage.

Automatic agent switchover now also applies to database ingestion and replication jobs that use the Query-based CDC method to capture changes from a Db2 for LUW, Oracle, or SQL Server source to a Cloud Data Lake target.

Application Ingestion and Replication

The October 2026 release of Application Ingestion and Replication includes the following new features and enhancements.

Additional targets for Application Ingestion and Replication

You can now use Microsoft Fabric Data Warehouse and Salesforce Data 360 targets with Oracle Fusion Cloud, Salesforce, SAP OData, and SAP ABAP sources, including SAP ECC and SAP S4/HANA with SAP Mass Ingestion Connector, for all load types in application ingestion and replication tasks.

All load types added for Cloud Data Lake targets with SAP OData

You can configure an application ingestion and replication incremental or combined load task from SAP OData to cloud data lake targets such as Amazon S3, Google Cloud Storage, Microsoft Azure Data Lake Storage Gen2, Microsoft Azure Synapse Analytics, Microsoft Fabric OneLake, and Oracle Cloud Infrastructure Object Storage. Previously, you could use these targets with SAP OData source for initial loads only.

Readable display values from Microsoft Dynamics 365 sources

When you create a task that uses Microsoft Dynamics 365 as the source, the task now writes the readable value for reference and coded fields to the target, next to the original column.

For OWNERTYPE and Lookup fields, the task adds a column named <ColumnName>_display_name that holds the display value, and the original column retains the GUID. For Choice, Yes-No, State, and Status fields, the task writes the label column <field>name, such as statuscodename, as a string column next to the numeric code. The target now holds both the reference and its resolved value. Existing tasks keep their current target columns. To add the display value columns, you need to redeploy your tasks.

Database Ingestion and Replication

The October 2026 release of Database Ingestion and Replication includes the following new features and enhancements.

Granular privileges for deploy, redeploy, and undeploy actions

As an administrator, you now have granular control over the deploy, redeploy, and undeploy actions on database ingestion and replication tasks through three separate feature privileges. You can restrict any of these actions for a role.

To let a user perform these actions, assign the Deploy Ingestion Task, Redeploy Ingestion Task, and Undeploy Ingestion Task feature privileges to the role.

For example, you can let a user run ingestion tasks but withhold the undeploy privilege. Previously, a Run permission combined the deploy, redeploy, start, stop, abort, and undeploy actions.

Note:

Effective in the October 2026 release, an organization-level flag controls these feature privileges. To enable this functionality for your organization, create a request with Informatica Global Customer Support. If you select and save these feature privileges, they won't take effect until Informatica Global Customer Support activates the functionality for your organization.

When enabled, the Admin, Deployer, and Designer system-defined roles include all three feature privileges by default, but custom roles don't. When a user in a custom role lacks these privileges, the Deploy, Redploy, and Undeploy options appear disabled in the ingestion and replication task setup flows, and don't appear in the Monitor and My Jobs menus or in Operational Insights. To grant these actions, an administrator must add the feature privileges to the custom role.

Microsoft Fabric Lakehouse target

You can now use Microsoft Fabric Lakehouse as a target for database ingestion and replication tasks of all load types.

To connect to a Microsoft Fabric Lakehouse target, use the Microsoft Fabric Lakehouse connector.

Oracle Autonomous Database target

You can now use Oracle Autonomous Database as a target in database ingestion and replication initial load tasks. To connect to a Oracle Autonomous Database target on Oracle Cloud Infrastructure, use the Oracle Autonomous Database connector.

Access Management for Oracle sources

You can now apply Cloud Data Access Management (CDAM) governance rules to Oracle source tables in database ingestion and replication jobs. In the Transform page of the task configuration, select one or more tables and add the Access Management transformation to assign de-identification and filtering policies defined in Cloud Data Governance and Catalog.

Connections available for Access Management in database ingestion and replication tasks

When you add access management to a database ingestion and replication task, the connection list on the Access Management page includes all the connections that match the source vendor type, including connections that are not Database Ingestion connections. Previously, the Access Management page listed only Database Ingestion connections, which meant that source vendors that required a non-ingestion connection, such as Oracle, had no available connection for access management configuration.

Encrypted Oracle source connection passwords

Data Ingestion and Replication extends the CLI password encryption to support Oracle-specific connection credentials. You can now provide encrypted values for the following fields:

The encryptText command introduces a new --method parameter with a selfcontained option. Unlike the existing keystore method, selfcontained embeds the encryption key directly in the encrypted output, and does no require a key-store.txt file on the machine that runs the CLI commands.

Multiple object distributors for Cloud Data Lake targets

You can configure multiple writer object distributors to run in parallel during initial load tasks for cloud data lake targets, including Microsoft Fabric OneLake, Amazon S3, Microsoft Azure Data Lake Storage Gen2, Google Cloud Storage, and Oracle Cloud Object Storage. Set the Writer Unload Multiple Distributors and Writer Distributor Count target custom properties to run multiple writer instances simultaneously to help the writer throughput keep pace with parallel source reads. Alternatively, enable Auto Tuning to calculate the optimal values automatically. For combined initial and incremental load tasks, multiple object distributors apply to the initial load phase in a synchronous mode only.

Soft Deletes for Microsoft Fabric Data Warehouse and Open Table targets

Database ingestion and replication incremental load jobs and combined initial and incremental load jobs can now process hard delete operations on the source as soft deletes on Microsoft Fabric Data Warehouse and Open Table targets. Database Ingestion and Replication marks the soft-deleted records with a "D" in the INFA_OPERATION_TYPE column on the target without actually deleting the records.

Truncate event handling for Oracle sources with Snowflake targets

Database ingestion and replication jobs that have an Oracle source can now detect TRUNCATE TABLE operations on an Oracle source table during log-based CDC replications to a Snowflake target. The incremental load task truncates the target table in standard apply mode or inserts a truncate record with an operation type of "T" in audit apply mode. You can configure this behavior with custom properties in the task configuration. You can also enable an alert that notifies you when the task detects a truncate event at the source.

File Ingestion and Replication

The October 2026 release of File Ingestion and Replication includes the following new features.

GCM cipher and RSA SHA-2 support for the Advanced SFTP V2 connector

You can use the Advanced SFTP V2 connector to connect to SFTP servers that require the aes128-gcm@openssh.com and aes256-gcm@openssh.com GCM ciphers. You can also use the connector to authenticate to SFTP servers that require the RSA SHA-2 host key algorithms rsa-sha2-512 or rsa-sha2-256. The connector also works with servers that still accept the older ssh-rsa algorithm, with no change to your connection configuration.

Improved security for Mass Ingestion service ports

The Mass Ingestion service uses internal service ports. These ports now bind to the local host (127.0.0.1), so processes running on the same machine as the Secure Agent can connect to them.