Table of Contents


  1. Abstract
  2. Informatica Installation
  3. Informatica Upgrade
  4. 10.1 Fixed Limitations and Closed Enhancements
  5. 10.1 Known Limitations
  6. Informatica Global Customer Support

Metadata Manager Fixed Limitations

Review the Release Notes of previous releases for information about previous fixed limitations.
The following table describes fixed limitations:
When you edit a related catalog object for an object in a custom resource, Metadata Manager might stop responding. When this occurs, the mm.log file shows a null pointer exception.
When you load an Informatica Platform resource using Metadata Manager 9.6.1 HotFix 2, the load fails with the following error:
Arithmetic overflow error converting expression to data type int.
Data lineage for a physical data object in an Informatica Platform resource shows bi-directional links between the physical data object and the corresponding database table, even though data lineage is in one direction.
Importing a model export file that includes rule set definitions fails when the domain uses Kerberos authentication.
Metadata Manager does not display data lineage links for an IBM DB2 for z/OS stored procedure when the CREATE PROCEDURE statement contains an INSERT INTO statement with a nested SELECT statement that contains a wildcard character to specify column names.
Metadata Manager displays backwards data lineage links between an IBM DB2 stored procedure and a table when the procedure inserts data into the table.
Loading a PowerCenter resource fails with the following database error when the resource contains a mapping that reads from an HDFS source file and loads data to a text file:
Invalid length parameter passed to the LEFT or SUBSTRING function.
Metadata Manager does not display data lineage links between a Netezza view and the tables from which it is created when the view definition contains the INTERSECT, MINUS, or UNION operations.
Metadata Manager displays incorrect data lineage links between a Teradata table and the corresponding view.
Metadata Manager does not display a link between a PowerCenter source qualifier and the database table when the source qualifier contains a specific SQL query.
Running data lineage might fail with an internal error when the diagram is very complex and you launch data lineage analysis from an end object.
A memory leak occurs in the SQL parser during resource load.
Metadata Manager does not display data lineage links for tables in stored procedures that contain an INSERT INTO statement when the statement uses a wildcard character to specify any column.
Loading a custom resource fails at the CSV to IME converter when an object name exceeds 255 characters in length.
Metadata Manager does not display data lineage between SAP R/3 tables and PowerCenter sessions when the connection to SAP is specified through a connection parameter and the parameter value contains lower case characters.
Exporting a data lineage diagram fails if the size of the data lineage diagram is too large for the web browser.
Loading a Cloudera Navigator resource fails when Cloudera Navigator becomes inaccessible after Metadata Manager extracts all of the JSON files.
Metadata Manager cannot display the impact summary for an object that has more than 1000 upstream or downstream impacted objects.
Simultaneously loading multiple PowerCenter resources with similar data sets and stored procedures fails with the following error:
An error occurred in LineageGraphInternalLinksCreationTaskHandler
When you select an object in a packaged resource and export it to a Microsoft Excel file, update either the business name or a custom attribute, and reimport the Excel file, the import might fail with the following error:
I/O error.
When you load an IBM DB2 9.7 resource with a specific SQL query in one of the views, the session S_M_ALLDB_VIEW_DEPS_EXTRACT terminates unexpectedly with the following error:
FATAL ERROR : An unexpected condition occurred in file [<path>/tpordvec.h] line [95]. Aborting the DTM process. Contact Informatica Global Customer Support.
Rule-based linking sometimes fails with a "Violation of PRIMARY KEY constraint" error.
Metadata Manager sometimes does not display data lineage links between a Teradata trigger and the table with which it is associated.
When you create an Informatica Platform 10.x resource, it can take more than 15 seconds for applications, parameter sets, and mappings to be displayed in the selection lists.