The April 2024 release of Data Ingestion and Replication includes the following changed behaviors.
Data type mapping for an SAP source and an Oracle target
When you configure an application ingestion task with an SAP source and an Oracle target, the CHAR data type of an SAP source is mapped to the VARCHAR2 data type of an Oracle target.
Previously, the CHAR data type of an SAP source was mapped to the CHAR data type of an Oracle target.
Default mapping of DATETIME and TIMESTAMP columns for a MySQL source and a SQL Server target
MySQL source DATETIME and TIMESTAMP columns that were previously mapped to a SQL Server DATETIME target column are now mapped to the SQL Server DATETIME2 column. This change was made to allow the whole range of source data to be correctly replicated to the target.
If you create and deploy a new task for an existing target table that contains a SQL Server DATETIME column, the table will be dropped and recreated. The table will not be dropped if an existing job is resumed or redeployed.
To avoid dropping an existing table, change the SQL Server DATETIME column to DATETIME2 column on the target side using the ALTER TABLE command.
Mass Ingestion sends a product tag to Databricks Delta when connecting to the target
When Mass Ingestion connects to a Databricks Delta target during an application ingestion or database ingestion job, it sends a special INFA_CMI_DATABRICKS tag as a key=value pair appended to the JDBC URL. Databricks Delta can use the tag to detect Informatica queries for data loading and to analyze Informatica consumption. On the Databricks Delta dashboard, the tag appears in the Query Source field.