PowerExchange Adapters for Informatica 10.1
- PowerExchange Adapters for Informatica 10.1
- All Products
You cannot use the distinct, sort, and join operations for Teradata source objects in a mapping that runs on the Blaze engine.
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.
When you run a mapping on the Blaze engine and the Teradata source or target contains Byte or Varbyte data type, the mapping fails.
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.
When you run a mapping on the Blaze engine and the Teradata source or target contains Unicode metadata, the mapping fails.
You cannot retrieve the mapping execution plan for Teradata mappings configured to run on the Blaze engine.
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.
If you add a Teradata source and a Teradata target in a mapping, and enable the Truncate Table option, the mapping might fail.
When you read data from two or more Teradata sources, you cannot override the source schema and source table name at run time.
When you create a Teradata Parallel Transporter API connection by using the infacmd isp CreateConnection command, you must enter even the optional fields.