Issue | Description |
|---|---|
CCORE-1834 | When you enable the staging optimization property for the source and run a parameterized mapping, the mapping task runs without optimizing the performance. (April 2023) |
Issue | Description |
|---|---|
ISD-6504 | When you write decimal values to an Avro file in an Amazon S3 target, certain decimal values are incorrectly written to the target. For example, the value 441265.1234 in the source is written as 4.412651234 in the target. (July 2025) |
Issue | Description |
|---|---|
MDMN-178716 | When you run a mapping task that uses a Business 360 FEP connection, the mapping task runs successfully but incorrectly displays the connection details from the log file as error messages. (October 2025) |
MDMN-160284 | When you import an existing mapping within a hierarchy to a target organization and run the mapping, the mapping fails with the following error: The schemas of the source table and target table do not match. Verify that the schemas match, synchronize the fields, and run the mapping again. (February 2025) |
MDMN-121918 | When you run mappings that use a Business 360 FEP connection, the mappings might fail intermittently with the following error: java.net.MalformedURLException: no protocol: null/metadata Workaround: To resolve this issue, see the Error: java.net.MalformedURLException Knowledge Base article. (May 2024) |
MDMN-65782 | In a target transformation, if you specify a hierarchy and one or more relationships within the hierarchy as multiple target objects in a single mapping, the mapping fails. (November 2023) |
MDMN-65803 | When you specify a relationship as the target object in a mapping, the connector catalog displays only the GUID values of the relationships instead of the display names. When you export these mappings, the GUID values change and prevent you from reusing the mapping. Workaround: After importing the mapping, manually specify the required relationship with the changed GUID value in the connector catalog and select Retain field Mapping check box. On the Field Mapping tab, choose Previous Mapping in the Automap list and run the mapping. (October 2023) |
MDMN-110788 | If a single mapping contains a hierarchy and relationships within the hierarchy as target objects, the mapping runs successfully but doesn't write any data to the target objects. (August 2023) |
MDMN-110787 | In a target transformation, if you specify relationships as multiple target objects, the mapping runs successfully for the first target object but fails for the rest. (August 2023) |
MDMN-112219 | When you use a Business 360 FEP connection to ingress a large number of records, the processing time is significantly high. (July 2023) |
MDMN-97751 | In a target transformation, if you map the sourcePkey field that contains special characters to the target field, the target transformation fails. Workaround: Use only the following special characters in the sourcePkey field: .~!/'={}|:@#$^&*()-_+,<>?` (July 2023) |
MDMN-96083 | When you map multiple targets to multiple target objects using a Business 360 FEP connector that uses a proxy-enabled Secure Agent, the mapping runs successfully even though the data doesn't get written to any of the target objects. Workaround. Disable the proxy server for the Secure Agent. (July 2023) |
MDMN-60298 | When you map two targets to two different business entities, the mapping runs successfully but writes all the data to one of the business entities and fails to write data to the other business entity. (July 2023) |
Issue | Description |
|---|---|
MDMN-153393 | When you configure multiple partitions in a Source transformation to export a large number of records, the mapping task uses only a single partition to process data during the extract step. (October 2024) |
MDMN-144495 | When you export hierarchies and relationships by using Business 360 FEP Connector, the egress job might fail at the stage step with the following error: Invalid JSON input: Unexpected character (July 2024) |
MDMN-144372 | When you export source records that contain validation errors, the exported data doesn't include the source systems of the field groups. The issue occurs only when the preview feature for validation errors is enabled in your organization. (July 2024) |
MDMN-123482 | When you export hierarchies and relationships that belong to a specific source system by using Business FEP Connector, the egress job exports hierarchies and relationships from all the source systems. (November 2023) |
MDMN-128369 MDMN-120462 | When you map the source fields that contain boolean values, such as true and false, to the target fields, the Business 360 FEP connector incorrectly processes both values as false. The Business 360 FEP connector processes them incorrectly because it identifies only 1 and 0 as boolean values. (October 2023) |
MDMN-65279 | A mapping does not reject the records that do not contain a value for the sourcePKey field. (January 2022) |
Issue | Description |
|---|---|
CCON-106033 | When you write to a Coupa target and select the PUT_RemitToAddresses_Suppliers_update operation in the Target transformation, the mapping fails with the following error: [ERROR] org.json.JSONException: JSONObject["supplier_id"] not found (May 2025) |
Issue | Description |
|---|---|
CCON-106328 | When you run a mapping enabled for SQL ELT optimization to write multi-line string fields to a flat file and the data is enclosed in double quotes, the data in incorrectly written to the target. (October 2025) |
CCON-105920 | When you run a Databricks mapping and use the Permanent IAM credentials authentication to stage data in Amazon S3, the mapping fails with the following error if the temporary security credentials for Amazon S3 expire: [ERROR] com.amazonaws.services.s3.model.AmazonS3Exception: The provided token has expired. Service: Amazon S3; Status Code: 400; Error Code: ExpiredToken; (October 2025) |
Issue | Description |
|---|---|
CCI-5192 | When you run a mapping in advanced mode to write data to multiple Databricks targets and view the job results, the Individual Task Results section doesn't display results for each target separately. Instead, it displays a single consolidated result for all targets. However, the data is correctly written to all targets. (April 2025) |
Issue | Description |
|---|---|
CCON-109034 | When you stage data in a Volume in a mapping that writes to a Databricks target, the mapping might fail with the following error or result in partial data loss in the target table: Error running query: [PATH_NOT_FOUND] org.apache.spark.sql.AnalysisException: [PATH_NOT_FOUND] Path does not exist: dbfs:/<VolumePath>. SQLSTATE: 42K03 (October 2025) Databricks ticket number: 00710956 |
CCON-70459 | When you read more than 10 GB of data from Databricks, the mappings intermittently fail with the following error: [ERROR] Read from Delta table failed (November 2023) Databricks ticket number: 2310230030003014 |
Issue | Description |
|---|---|
CCON-106600 | When you use Workload Identity Federation authentication to connect to Google BigQuery, browsing metadata might take longer than expected if the project contains a large number of datasets. (October 2025) |
CCON-105684 | When you configure the read mode as staging and use the Parquet staging file format in a Source or Lookup transformation, the Byte data type exceeding 4000 bytes gets truncated. (May 2025) |
CCON-103155 | When you run a mapping enabled with SQL ELT optimization and use the +, -, *, and % operators within an Expression transformation inside parentheses, the query result might be incorrect because the parentheses for these operators are not honored and are removed from the query. (April 2025) |
Issue | Description |
|---|---|
CBDM-38003 | When you run a mapping configured with SQL ELT mode that contains a Joiner, Lookup, or Normalizer transformation connected to another Normalizer transformation, the mapping fails with the following error: An error occurred during mapping translation: Internal error. (April 2025) |
Issue | Description |
|---|---|
CCON-107688 | An IBM MQ mapping continues to run even when the connection to IBM MQ Queue Manager is broken. (October 2025) |
CCON-106121 | When you write to the Correlid message header field in an IBM MQ mapping, the mapping writes junk characters to the Correlid message header field in the IBM MQ target. (October 2025) |
CCON-106115 | When you migrate and run an IBM MQ mapping in another environment and you have the required authorities only on the message queue and Queue Manager component in IBM MQ, the mapping fails. (October 2025) |
Issue | Description |
|---|---|
CBDM-39280 | When you use the None format type to read Gzip compressed files, the mapping fails with the following error: The compression format [Gzip] is not valid. (October 2025) |
Issue | Description |
|---|---|
CCON-108575 | When you configure Managed Identity authentication to connect to Microsoft Azure Data Lake Storage Gen2 and run multiple pipelines or write to multiple targets using Iceberg or Delta file formats, the mapping might fail with the following error: Temporarily throttled, too many requests (October 2025) Apache ticket number:14039 |
Issue | Description |
|---|---|
CCON-98329 | When you enable dynamic schema handling in a task to run a mapping in advanced mode and select Parquet as the staging file format, the mapping fails. (July 2024) |
Issue | Description |
|---|---|
CCON-105770 | When you create a Microsoft Fabric Data Warehouse target at runtime where incoming string fields have a precision greater than 4000, the mapping automatically sets the precision to 8000 in the target without preserving the precision of the incoming field. (July 2025) |
CCON-103782 | When you map a date or datetime field in the source to a string data type in the target, the mapping writes data to the target in the MM/dd/yyyy hh:mm:ss format, a 12-hour format, instead of the MM/dd/yyyy HH:mm:ss format, a 24-hour format. This results in a data mismatch with the source. (April 2025) |
CCON-103362 | When you write to a Microsoft Fabric Data Warehouse target, the mapping might fail with the following error if the staging table in Microsoft Fabric Lakehouse is not accessible: Failed to execute the command after the 4 retry attempts and the following error occurred: [java.lang.RuntimeException: java.lang.RuntimeException: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'TestSyncLH.dbo.TempTable_e305ce21-fc49-4f08-ae7d-638e63bbfaf7'.] (October 2025) Microsoft ticket number: 2501090040011982 |
Issue | Description |
|---|---|
CCON-108634 | When you run multiple mappings concurrently to write to a Microsoft Fabric Data Warehouse target, the mappings fail with the following error: MD Refresh Response code:400 Workaround: Reduce the number of concurrent mappings. (October 2025) Microsoft ticket number: 2509090040002501 |
Issue | Description |
|---|---|
PWXCLD-295 | The Microsoft SQL Server CDC mapping task fails with the following error for a table or columns with special characters in their names: Internal error. The DTM process terminated unexpectedly. Contact Informatica Global Customer Support. |
Issue | Description |
|---|---|
CCON-103563 | When you run a MongoDB V2 mapping to write data to a MongoDB V2 target configured with a primary key update column in the Target transformation, the mapping updates or upserts data only in the first row that contains the same primary key value. (July 2025) |
CCON-103535 | Although a source field of Double data type contains a Null value, the mapping writes 0 to the target instead of maintaining the Null value for the Double data type. (April 2025) |
Issue | Description |
|---|---|
CCON-108605 | When you read from an Apache Iceberg table that has deleted or updated rows history, the mapping stops responding, and the session log displays the following error: [ERROR] java.lang.NoClassDefFoundError: org/roaringbitmap/longlong/Roaring64Bitmap (October 2025) |
Issue | Description |
|---|---|
CCON-98664 | When you run a mapping to write data to a column with NVARCHAR2 data type, and the source data length exceeds the precision set for the target object, the rows are rejected with the following warning message: ERROR: Writer execution failed. Database error: [0] [ FnName: Execute - [Informatica][ODBC Oracle Wire Protocol driver][Oracle]ORA-12899: value too large for column <schema name>.<table name>.<column name> (actual: 100, maximum: 50) ] For more information about the fixed issue and to apply the updates, see How to configure the updated ODBC EBF driver with Oracle Connector Knowledge article. (October 2025) |
Issue | Description |
|---|---|
CCON-108161 | When an SAP BW mapping contains an InfoObject configured with custom fields using the Add Field option in the SAP system, the Fields tab for the SAP BW source doesn't list all fields available for the mapping. (October 2025) |
Issue | Description |
|---|---|
CCON-109140 | When you run an SAP OData V4 mapping that reads data from flat entities in SAP Datasphere applications, the mapping might fail with the following error in the session log: 401 Unauthorised error (October 2025) |
Issue | Description |
|---|---|
CCON-105730 | When you configure an uncached Lookup transformation to look up data of the DATN or TIMN data type from an SAP table source, the mapping fails with the following error: [ERROR] Received the following error from SAP: [An exception with the type CX_SY_OPEN_SQL_DATA_ERROR was raised, but was not handled locally or declared in a RAISING clause.] (July 2025) |
Issue | Description |
|---|---|
CCON-106442 | When you run a mapping in SQL ELT mode to write data of the Decimal data type to a Snowflake target from an Amazon S3 or Microsoft Azure Data Lake Storage Gen2 source, the mapping writes the Decimal data type with a default scale of 0. (July 2025) |
CCON-39088 | A mapping fails without an error message in the session log and continues to run post-SQL statements specified for the target. Solution: Add the -DSNOWFLAKE_SKIP_TARGET_POSTSQL_ON_ERROR JVM option property value to true in the Secure Agent properties. (July 2025) |
Issue | Description |
|---|---|
CLDDI-39533 | Although you change the metadata of source fields using the Edit Metadata option in the Fields tab, the mapping task that is based on a mapping in SQL ELT mode ignores metadata changes and recreates the table with its original metadata when all the following scenarios are true:
(April 2025) |
Issue | Description |
|---|---|
CCON-106378 | When you run a mapping in advanced mode to write data to an Apache Iceberg target table that is enabled with the Truncate Target Table option in the Target transformation, the mapping fails. Workaround: Disable the Truncate Target Table option for the target in the Target transformation. (July 2025) Snowflake ticket number: 01041084 |
Issue | Description |
|---|---|
CCI-5577 | When you run a mapping configured with a simple filter to filter data from a related object and the parent object contains the same field name that you add in the filter condition for the related object, the mapping fails with the following error: Invalid expression string for filter condition (July 2025) |