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 |
|---|---|
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 |
|---|---|
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-111787 | When you use the Databricks JDBC driver version 2.7.5, you cannot configure an unauthenticated proxy. (April 2026) Databricks ticket number: 00838573 |
CCON-111833 | When you use the Databricks JDBC driver version 2.7.1 and 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 |
|---|---|
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 2026) |
Issue | Description |
|---|---|
CCON-93048 | You can't prevent partial data upload to a Google Cloud Storage target location when a mapping fails at runtime. (April 2026) |
Issue | Description |
|---|---|
CCON-108298 | An IBM MQ mapping continues to run even when the source connection to IBM MQ Queue Manager is broken. (April 2026) |
Issue | Description |
|---|---|
CBDM-39940 | When a mapping in advanced mode runs successfully, a NullPointerException stack trace is logged in the driver logs. Workaround: Ignore the exception. (April 2026) |
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-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 (April 2026) |
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-105131 | When you use Teradata subtype in the connection and run a mapping enabled with SQL ELT optimization, you can't perform update and delete operations when the NOT NULL columns in the target table are unmapped. (April 2026) |
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 (April 2026) |
Issue | Description |
|---|---|
CCON-111700 | When you create a target object at run time to write data to Apache Iceberg tables managed by the AWS Glue catalog, or run a mapping with dynamic schema handling with alter and apply changes enabled, the mapping fails if the incoming field names are not in lowercase. (April 2026) |
Issue | Description |
|---|---|
CCON-110584 | When an input field of UUID data type is mapped to an in or inout UUID parameter in a stored procedure in an SQL transformation, the mapping fails at runtime with the following error: [FATAL] Postgres Stored Procedure [insert_order_with_params] call failed with error\: [informatica][PostgreSQL JDBC Driver][PostgreSQL]procedure cloud.insert_order_with_params(unknown, character, unknown) does not exist. No procedure matches the given name and argument types. You might need to add explicit type casts. Data Direct ticket number: 01825293 (April 2026) |
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. (April 2026) |
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 (April 2026) |
CCON-108436 | An SAP OData V4 mapping that uses a proxy server to connect to SAP Datasphere fails to fetch the object metadata at design time. (April 2026) |
Issue | Description |
|---|---|
CCON-110178 | Data corruption might occur in the target when you write data to an SAP table. (April 2026) |
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) |