Table of Contents

Search

  1. Abstract
  2. Informatica Installation
  3. Informatica Upgrade
  4. Informatica Closed Enhancements
  5. Informatica Fixed Limitations
  6. Informatica Known Limitations
  7. Informatica Third-Party Limitations
  8. Informatica Global Customer Support

Big Data Third-Party Limitations

Big Data Third-Party Limitations

The following table describes a third-party limitation:
CR
Description
429137
Mappings that use the Blaze engine on a MapR cluster fail if the path to the MapR distribution folder is too long.
Workaround: Create a symbolic link to the MapR distribution folder.
Run the following command on every node in the Hadoop cluster:
ln -s <Informatica installation directory>/services/shared/hadoop/mapr_<version> <link name>
After you create the symbolic link, you must add it to the
infagrid.dis.hadoop.dist
property in
hadoopEnv.properties
and the MAPR_HOME system environment variable.
410437
If the user name or password for a target IBM DB2 table is more than eight characters, the mapping fails to run in the Hive environment and the following error appears in the Hadoop cluster logs:
Caused by: java.io.IOException: Mapping execution failed with the following error: WRT_8001 Error connecting to database... WRT_8001 [Session Write_EMP_OUT5_MAPPING_3285816766724683 Username test_it2 DB Error -1 [IBM][CLI Driver] SQL30082N Security processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID"). SQLSTATE=08001
Workaround: Verify that the IBM DB2 database user name and password is less than eight characters.
398978
Mapping fails if it uses the Teradata Connector for Hadoop (TDCH) to run on a Hadoop cluster that uses Kerberos authentication.
Workaround: Use the kinit command to generate a valid ticket on all the cluster nodes before you run the mapping.


Updated October 25, 2018