Metadata Manager 10.1
- Metadata Manager 10.1
- All Products
When you install Big Data Management on Cloudera by using Cloudera Manager, the parcels are not copied to .flood directory and the installation fails with the following error:
Src file /opt/cloudera/parcels/.flood/INFORMATICA-10.1.0.informatica10.1.0.p1.364-sles11.parcel/INFORMATICA-10.1.0.informatica10.1.0.p1.364-sles11.parcel does not exist.
Also, after you uninstall Big Data Management on Cloudera by using Cloudera Manager, the parcels are not deleted from the .flood directory.
Cloudera reference number: 103733
When you use the Netezza ODBC driver and write Unicode data to a Netezza database, the mapping might fail when the Netezza target contains Varchar columns. The mapping fails because of a DataDirect Driver Manager issue.
DataDirect reference number: 00343606
The Spark engine does not return output for a master or detail outer join when the condition does not join on keys, but it compares a column with a constant or null.
Apache JIRA reference number: https://issues.apache.org/jira/browse/SPARK-14854
When you use a JDBC connection in the Developer Tool to import a Netezza source object that contains the time data type, the data preview fails.
When you use authorization through user impersonation on a MapR cluster, the mapping fails with an error like:
MapR issue reference number: 00037816
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.
DataDirect reference number: 00343606
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.
Workaround: Set the Operating System Profile and Impersonation in the Data Integration Service to false and then run the mapping.
Teradata case number: RECGV4J3Q
When you import data from an Oracle database through Sqoop and the database contains a column of the Clob data type, the mapping fails.
Sqoop ticket reference number: SQOOP-2945
Loading a Microsoft SQL Server resource fails when TLS encryption is enabled for the source database and the Metadata Manager repository is a Microsoft SQL Server database with TLS encryption enabled.
Data Direct case number: 00343832
Profile fails with an ambiguous column reference reror when you run a profile with domain discovery on a MapR 4.0.2 YARN aand MapR 4.0.2 distribution.
When you use an ODBC connection to write data to a Teradata client version 184.108.40.206, the Data Integration Service rejects data of the numeric data type.
Teradata ticket reference number: RECGNXLML
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.
DataDirect case reference number: 00324380
When you run a data domain discovery profile with multiple data domains on MapR 4.0.2 Yarn or MapR 4.0.2 classic Hadoop distribution files, profile run fails.
When you preview data from the SAP HANA database for a decimal data type with a precision of 38 digits, the data preview runs continuously. When you run the mapping, the mapping run fails with an error.
SAP ticket reference number: 0000624569 2015
When you import a Timestamp with Time Zone metadata, the scale appears as 0 instead of 6 for the data type.
DataDirect reference number: 00310850
On AIX operating systems, when you enable secure communication to an SAP HANA database on AIX with the SSL protocol, mappings terminate unexpectedly.
SAP ticket reference number: 0001101086
Mapping fails in the Hive environment if the user name or password for a target IBM DB2 table is more than eight characters. 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.
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.
When a MySQL table name contains special characters, the Developer tool does not import all the columns. This issue occurs when you use the DataDirect ODBC and JDBC drivers to import the metadata.
DataDirect ticket reference number: 00322369
You cannot configure an Oracle 12c database for Kerberos authentication.
Oracle SR number: 3-8990776511
Sessions that read data from an Oracle source or write data to an Oracle target might fail when secure communication is enabled for the Oracle database. A session is more likely to fail when it performs a database lookup against a secure Oracle database.
Workaround: Contact Informatica Global Customer Support. Reference Oracle SR number: 3-8287328531.
You cannot create an Oracle resource when secure communication is enabled for the Oracle metadata source. Similarly, you cannot set up the Metadata Manager repository on an Oracle database when secure communication is enabled.
Oracle SR number: 3-8287328531