Cloud Data Integration Connectors All Products
When you run a mapping that contains two target transformations of the same target object and uses different connection objects for both target transformations, and you configure an update operation with a key selected on the first target transformation, an insert operation on the second target transformation, the mapping fails with the following error:
Workaround: Perform any of the following actions:
When you use a custom query as a source in a mapping and the query returns two or more columns with the same name, the metadata fetch fails.
Workaround: Use aliases for the column names that are same.
When a mapping contains multiple targets and the targets have different key columns, the mapping task fails with the following error:
[ERROR] com.informatica.powercenter.sdk.SDKException: Invalid operation field name.
When you configure a non-CDC source and select
Treat Source Rows Asunder advanced target properties, the task fails.
Workaround: Select the operation you want to perform in
Treat Source Rows Asunder advanced target properties.
When you configure an unconnected lookup in a mapping, the following error is displayed:
Unconnected lookup supports only relational and flat file connections.
When you run a mapping that contains an uncached lookup, the mapping fails with the following error:
[ERROR] com.informatica.cci.cloud.client.impl.CCIClientExceptionImpl: Invalid expression string for filter condition.
When you read nchar or nvarchar columns from a source and create a Microsoft Azure SQL Data Warehouse V3 target at run time to write data, the mapping fails with the following error:
Cannot create target for transformation Target due to the following reason: [The size (8000) given to the type 'COL_NTEXT' exceeds the maximum allowed (4000).].
The Monitor does not show the rejected row count. It shows the total source processed row count.
Workaround: Check the session log for correct row statistics for rejected rows and processed rows.
When you run a mapping to read a source that contains special characters in the field names and select the Create Target option to write data to a Microsoft Azure SQL Data Warehouse V3 target, the mapping fails.
Data Preview does not display data for binary or varbinary columns for Microsoft Azure SQL Data Warehouse V3 objects
When you read data from a source that contains varbinary columns, the Secure Agent reads the empty values for varbinary columns as NULL.
The session load summary in the session log is not captured for each commit interval.
When you run a mapping to read a source that contains unicode characters in the field names or values and write data to a Microsoft Azure SQL Data Warehouse V3 target, the mapping fails.
The session log does not show the reject row count in the row statistics.
Workaround: To log the reject row count, set the
Reject Thresholdin the target properties. Open the session log to see the reject files names that are created in the Microsoft Azure Blob container and open the reject files to see the details.
When you upsert or update data to Microsoft Azure SQL Data Warehouse and more than one column in the source table contains the same value as the target column on which the primary key is defined, the Secure Agent updates data incorrectly.
When you use a lookup condition on a Microsoft Azure SQL Data Warehouse object and schedule the task to run later, the task fails to respond.