Metadata Manager All Products
A dynamic mapping with an Update Strategy transformation fails at run time when one of the following conditions is true:
You cannot preview flat file data if the flat file uses a four-byte UTF-8 format.
When you run multiple concurrent mappings with Lookup and Sorter transformations in the native environment, the mappings might hang.
When you import a mapping from PowerCenter that contains a mapplet and an Expression transformation, the following error sometimes appear in the log:
The transformation instance cannot be connected to the active transformations.
Workaround: Ignore the error and import the mapping.
When you run data preview on an Oracle table with a native SSL connection or you run a mapping that has an Oracle data object with a native SSL connection, the Developer tool shuts down unexpectedly. (393023)
You cannot use the keyboard to add an HTTP web connection.
Workaround: Use the mouse to add an HTTP web connection.
You cannot use the keyboard to add a web service connection.
Workaround: Use the mouse to add a web service connection.
When you create an Oracle connection with a case-sensitive user name, the Developer tool does not display the default schema. (421946)
The Developer tool imports the DECFLOAT data type of IBM DB2 for z/OS tables as Char(0). (455216)
If the ODBC data source contains a special character in a column name, mappings that read data from or write data to Microsoft SQL Server databases fail.
On AIX 7.1, if you use the Oracle 12c client to connect to an Oracle database, and enable TLS 1.2 encryption for the Oracle 12c client, the mapping fails.
Mappings that contain columns of the Timestamp with Time Zone data type fail if you do not install the Microsoft Visual C++ 2010 Redistributable Package on the server machine.
When you import Teradata and Netezza mappings that contain stored procedures or SQL transformations from PowerCenter to the Developer tool, the import fails. (461184)
If the SQL query in an SQL transformation contains a decimal 38 column with a large precision, the Data Integration Service truncates the scale. This issue occurs if you enable high precision to read data from Oracle.
When you rename a port that is referenced in an invalid expression or an expression that does not support null values as arguments, the port is not renamed and mapping validation fails with the following error: [<original port name>: invalid symbol reference].