Table of Contents

Search

  1. Abstract
  2. Installation and Upgrade
  3. 10.2 HF1 Fixed Limitations and Closed Enhancements
  4. 10.2 HF1 Known Limitations
  5. 10.2 Fixed Limitations and Closed Enhancements
  6. 10.2 Known Limitations
  7. Emergency Bug Fixes Merged into 10.2
  8. Informatica Global Customer Support

Third-Party Fixed Limitations (10.2)

Third-Party Fixed Limitations (10.2)

Review the Release Notes of previous releases for information about previous fixed limitations.
The following table describes fixed limitations:
Bug
Description
PLAT-17502
The environment variable INFA_ODBCTRACEFILE does not generate driver level trace logs that are necessary to troubleshoot connectivity errors for the Informatica Data Services Native ODBC driver.
DataDirect reference number: 02094112
OCON-1308
If a Teradata target contains a column of the CHAR or VARCHAR data type at the fifth position, the Data Integration Service writes NULL values to the column. This issue occurs when you use an ODBC connection to write data. (439606)
DataDirect case reference number: 00324380
OCON-1081
When you use the Teradata ODBC driver and write Unicode data to a Teradata database, the mapping might fail when the Teradata target contains Varchar columns. The mapping fails because of a DataDirect Driver Manager issue. (458899)
DataDirect reference number: 00343606
BDM-5217
When you test an HDFS connection to the HDInsight cluster from the Developer tool, the test connection fails with the following error:
org.apache.hadoop.fs.azure.AzureExceptionom : org.apache.hadoop.fs.azure.KeyProviderException: java.io.IOException: Cannot run program '/usr/lib/python2.7/dist-packages/hdinsight_common/decrypt.sh': CreateProcess error=2
BDM-5022
When you run a mapping with the Spark engine on a MapR cluster, the execution engine uses the default MapR staging directory and not the staging directory that you configured in the "SPARK HDFS Staging Directory" property in the Hadoop connection.
For example, the engine uses the directory /user/<Data Integration Service username>/. If you configured the impersonation user, the engine uses the directory /user/<impersonation user>. If you configured the operating system profile (OSP) user, the engine uses the directory /user/<OSP user>.
MapR case number 00045736.
BDM-1992
If you set the Operating System Profile and Impersonation to true for the Data Integration Service and the Available Operating System Profile to OSP1 in the Developer client, and run a Teradata mapping in native mode, the mapping fails.
Teradata case number: RECGV4J3Q


Updated June 29, 2020