Table of Contents

Search

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

PowerExchange Adapters for Informatica Release Notes (10.5.0.1)

PowerExchange Adapters for Informatica Release Notes (10.5.0.1)

PowerExchange for JD Edwards EnterpriseOne (10.5)

PowerExchange for JD Edwards EnterpriseOne (10.5)

Known Issues

The following table describes known issues:
Bug
Description
OCON-11523
When you import a table that contains the ID_LONG data type, the Integration Service fails to import some of the table columns.
OCON-11456
Even when the error threshold is reached, the Integration Service continues to process the data and mapping does not fail. The issue occurs because the Stop On Errors run-time property does not work.
OCON-11372
If the Integration Service writes rejected rows followed by valid rows to an interface table, the row statistics generated for an InterfaceWrite operation is incorrect.
OCON-11223
When you apply a native filter expression for data that contains the JDE date data type format that is not valid, the data preview and mapping does not fail. An appropriate error message does not appear when you use formats that are not valid.
Workaround: Do not use the yyyy-mm-dd hh:mm:ss and hh:mm:ss date formats. Instead, use the yyyy-mm-dd format.

0 COMMENTS

We’d like to hear from you!