Table of Contents

Search

  1. Abstract
  2. 2020 - August
  3. 2020 - July
  4. 2020 - April
  5. 2020 - February
  6. 2020 - January
  7. 2019 - November
  8. 2019 - September
  9. 2019 - August
  10. 2019 - July
  11. 2019 - June
  12. 2019 - May
  13. 2019 - April
  14. 2019 - March
  15. Informatica Global Customer Support

Connector Release Notes

Connector Release Notes

Microsoft Azure SQL Data Warehouse V3 Connector Known Limitations

Microsoft Azure SQL Data Warehouse V3 Connector Known Limitations

The following table describes known limitations:
CR
Description
IF-28468
When you run a mapping to update a Microsoft Azure SQL Data Warehouse target table that has more than 750 columns, the mapping fails.
CCON-21346
When you use the
Create Target
option in an
elastic mapping
, the Secure Agent writes Bigint values as NULL in the target file.
CCON-20702
When you configure a
Query Options Filter
on a Date field, the mapping fails with an internal server error.
Workaround: Use advanced filters to configure a filter on a Date field and run the mapping again.
CCON-20337
When you use the
Create Target
option, select
Data Driven
in
Operation
, and specify a data driven condition in a mapping, the mapping fails with the following error:
No keys selected for Update/Delete Operation
However, an empty target table is created.
CCON-20077
When you use the
Create Target
option and run a mapping to write a real data type from a Microsoft Azure SQL Data Warehouse source to a Microsoft Azure SQL Data Warehouse target, the mapping fails.
CCON-18378
When the Secure Agent machine is outside the virtual network (VNet) and you connect to Microsoft Azure Blob Storage or SQL Data Warehouse VNet endpoints,
Test Connection
fails.
Workaround: In addition to the
Virtual Network
section, configure the Secure Agent IP in the
Firewall
section and test the connection again.
CCON-17208
When you use an ODBC data source to connect to a Microsoft Azure SQL Data Warehouse case-sensitive database and if a mapping uses multiple sources or targets with the same name and different columns, the mapping fails with an invalid column names error.
CCON-16927
When the source or target Microsoft Azure SQL Data Warehouse tables contain unicode characters in the table name or column names, the mapping fails with the following error:
Unexpected process transformation error, transformation: 'Source' (Source), error: 'null'
CCON-16063
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.
CCON-15523
When you use custom SQL query as a source and map a float data type to a target, the mapping fails.
Workaround: Use a table source instead of custom SQL query.
CCON-15409
When you run a mapping that reads a large volume of data from or writes a large volume of data to Microsoft Azure SQL Data Warehouse, the mapping or the task fails with a Java heap space error.
Workaround: Set the JVM options for type Tomcat JRE to increase the -Xms and -Xmx values in the system configuration details of the Secure Agent. You must then restart the Secure Agent.
CCON-15333
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.
CCON-15066
When you map a
datetime
value from an expression using a
system timestamp
function to a Microsoft Azure SQL Data Warehouse target, the mapping fails.
CCON-14464
When you configure an unconnected lookup in a mapping, the following error is displayed:
Unconnected lookup supports only relational and flat file connections.
CCON-14462
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.
CCON-14276
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).].
CCON-14259
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.
CCON-14249
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.
CCON-14226
Data Preview does not display data for binary or varbinary columns for Microsoft Azure SQL Data Warehouse V3 objects.
CCON-14098
The session load summary in the session log is not captured for each commit interval.
CCON-14061
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.
CCON-13972
The session log does not show the reject row count in the row statistics.
Workaround: To log the reject row count, set the
Reject Threshold
in 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.
CCON-10291
When you use an ODBC data source to connect to Microsoft Azure SQL Data Warehouse and the target table has an IDENTITY column, the Update operation fails.
CCON-8395
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.
CCON-7730
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.


Updated August 02, 2020