Table of Contents

Search

  1. Abstract
  2. PowerExchange for Amazon Redshift
  3. PowerExchange for Amazon S3
  4. PowerExchange for Cassandra
  5. PowerExchange for Google Analytics
  6. PowerExchange for Google BigQuery
  7. PowerExchange for Google Cloud Spanner
  8. PowerExchange for Google Cloud Storage
  9. PowerExchange for Greenplum
  10. PowerExchange for HBase
  11. PowerExchange for HDFS
  12. PowerExchange for Hive
  13. PowerExchange for JDBC V2
  14. PowerExchange for JD Edwards EnterpriseOne
  15. PowerExchange for Kudu
  16. PowerExchange for LDAP
  17. PowerExchange for Microsoft Azure Blob Storage
  18. PowerExchange for Microsoft Azure Cosmos DB SQL API
  19. PowerExchange for Microsoft Azure Data Lake Storage Gen1
  20. PowerExchange for Microsoft Azure Data Lake Storage Gen2
  21. PowerExchange for Microsoft Azure SQL Data Warehouse
  22. PowerExchange for Microsoft Dynamics CRM
  23. PowerExchange for MongoDB
  24. PowerExchange for Netezza
  25. PowerExchange for OData
  26. PowerExchange for Salesforce
  27. PowerExchange for SAP NetWeaver
  28. PowerExchange for Snowflake
  29. PowerExchange for Tableau
  30. PowerExchange for Tableau V3
  31. PowerExchange for Teradata Parallel Transporter API
  32. Informatica Global Customer Support

PowerExchange Adapters for Informatica Release Notes

PowerExchange Adapters for Informatica Release Notes

PowerExchange for Microsoft Azure SQL Data Warehouse (10.5.2)

PowerExchange for Microsoft Azure SQL Data Warehouse (10.5.2)

Fixed Issues

The following table describes fixed issues:
Bug
Description
OCON- 28944
When you run multiple Microsoft Azure SQL Data Warehouse mappings in a batch that point to the same Microsoft Azure Data Lake Storage Gen2 file system, certain mappings fail with the following error:
Error : External file access failed because the specified path name does not exist. Enter a valid path and try again.
OCON-28603
When you use Azure Active Directory authentication to connect to Microsoft Azure SQL Data Warehouse, the test connection fails.
OCON-28588
When you run a Microsoft Azure SQL Data Warehouse mapping and the native name of a column contains a space, the mapping fails with the following error:
The name cannot contain spaces.

Known Issues

The following table describes known issues:
Bug
Description
OCON-29268
When you run a dynamic mapping to read data from Microsoft Azure Data Warehouse and the column name contains unicode characters, the mapping fails with the following error:
Exception occurred while validating record metadata: ??????_bigint1 is invalid field name

0 COMMENTS

We’d like to hear from you!