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

Informatica Developer Third-Party Limitations

Informatica Developer Third-Party Limitations

The following table describes third-party known limitations:
CR
Description
442760
When you use an ODBC connection to write data to a Teradata client version 15.10.0.1, the Data Integration Service rejects data of the numeric data type.
Teradata ticket reference number: RECGNXLML
439606
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
438965
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.
424900
Validation errors might occur when you validate logical data object models that created from .xsd files that define a Sybase data object schema. The validation errors report precision and data type matching errors.
Workaround: Manually correct mismatched data types in the logical data object model before you proceed.
MITI case number: INFADEV-41
414220
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
413119
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
410495
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
395943
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


Updated October 25, 2018