Table of Contents

Search

  1. Informatica Bug Tracking System Change
  2. Upgrade Support
  3. PowerExchange for Amazon Redshift
  4. PowerExchange for Amazon S3
  5. PowerExchange for Cassandra
  6. PowerExchange for DataSift
  7. PowerExchange for Facebook
  8. PowerExchange for Greenplum
  9. PowerExchange for HBase
  10. PowerExchange for HDFS
  11. PowerExchange for Hive
  12. PowerExchange for JD Edwards EnterpriseOne
  13. PowerExchange for LDAP
  14. PowerExchange for LinkedIn
  15. PowerExchange for MapR-DB
  16. PowerExchange for Microsoft Azure Blob Storage
  17. PowerExchange for Microsoft Azure SQL Data Warehouse
  18. PowerExchange for Microsoft Dynamics CRM
  19. PowerExchange for MongoDB
  20. PowerExchange for Netezza
  21. PowerExchange for OData
  22. PowerExchange for Salesforce
  23. PowerExchange for SAP NetWeaver
  24. PowerExchange for Tableau
  25. PowerExchange for Teradata Parallel Transporter API
  26. PowerExchange for Twitter
  27. PowerExchange for Web Content-Kapow Katalyst
  28. Informatica Global Customer Support

PowerExchange Adapters for Informatica Release Notes

PowerExchange Adapters for Informatica Release Notes

PowerExchange for Teradata Parallel Transporter API Known Limitations (10.1.1)

PowerExchange for Teradata Parallel Transporter API Known Limitations (10.1.1)

The following table describes known limitations:
Bug
Description
OCON-5769
When you use the native Teradata Connector for Hadoop to run a mapping that contains a filter transformation, the Developer Tool pushes the filter transformation logic to the source even though you do not set the optimization level.
OCON-1241
When you run a mapping on the Blaze engine to read from or write data to Teradata, the session load summary shows an incorrect row count of zero. (460132)
OCON-1197
When you apply a filter condition on multiple ports either in the filter transformation or in the filter property of a Teradata source object, mapping fails on the Blaze engine. (460503)
OCON-983
If a Teradata mapping fails when the error limit is reached, the Teradata target table gets locked. When you run the mapping again, the mapping fails because the target table is locked. This issue occurs when you use the Load operator. (443157)
OCON-877
When you run a mapping on the Blaze engine and the Teradata source or target contains Byte or Varbyte data type, the mapping fails. (460491)
OCON-703
You cannot use the distinct, sort, and join operations for Teradata source objects in a mapping that runs on the Blaze engine. (460868 )
OCON-658
When you read data from two or more Teradata sources, you cannot override the source schema and source table name at run time. (439256)
OCON-554
When you create a Teradata Parallel Transporter API connection by using the infacmd isp CreateConnection command, you must enter even the optional fields. (438441)
OCON-350
When you run a mapping on the Blaze engine and the Teradata source or target contains Unicode metadata, the mapping fails. (457906)