Table of Contents


  1. Abstract
  2. Installation and Upgrade
  3. 10.2 HF1 Fixed Limitations and Closed Enhancements
  4. 10.2 HF1 Known Limitations
  5. 10.2 Fixed Limitations and Closed Enhancements
  6. 10.2 Known Limitations
  7. Emergency Bug Fixes Merged into 10.2
  8. Informatica Global Customer Support

Metadata Manager Fixed Limitations (10.2 HotFix 1)

Metadata Manager Fixed Limitations (10.2 HotFix 1)

Review the Release Notes of previous releases for information about previous fixed limitations.
The following table describes fixed limitations:
When you load a PowerCenter resource Metadata Manager does not replace the parameters for flat file names and flat file path with actual values.
When you create a view on a table alias in an IBM DB2 for z/OS resource, incorrect lineage appears between two views in the resource.
If you use enumerated links to define data lineage relationships between the business terms in Metadata Manager, the links for business glossary terms do not appear in the Analyst tool.
In the
Exported Missing Link Details
Missing Link Details
worksheet, the
Expected Table
column incorrectly lists multiple tables that are aliases within the PowerCenter SQLOverride statement.
An error appears when you load the Teradata resources in Metadata Manager.
Sometimes, a null pointer exception appears when you run the lineage on a versioned PowerCenter repository object.
Schedule name is not updated when the following conditions are true:
  1. You attach a schedule to a resource.
  2. You export the resource.
  3. In the resource configuration file, you change the schedule name to an existing schedule name in the Metadata Manager warehouse.
  4. You import the resource configuration file into the Metadata Manager warehouse.
Incorrect lineage appears for PowerCenter resources if you partially parameterize the source table name.
In an Oracle resource, when you create a lineage between a table and schema that are in the same schema, links do not appear between the table and schema.
After you modify an enumerated links file, if you remove the links for a business glossary term and reload the resource, the links are not removed in the
Related Catalog Object
section for the term.
The LDAP account is locked when the following conditions are true:
  1. You create a business glossary resource.
  2. You change the password for the LDAP principal user.
  3. You delete or purge the business glossary resource.
Informatica Analyst on an LDAP security domain stops responding when you load a business glossary resource that has more than 30,000 links.
Linking between resources fail if you schedule a resource load in the Kerberos environment.
When the schema name in a Teradata resource exceeds 30 characters, the schema name is truncated in the Metadata Manager.
Sometimes, the Teradata resource load fails with the stringIndexOutofBounds exception.
An error appears when you use the rule-based links to link PowerCenter resource and Netezza resource.
When you export the lineage for a Teradata view to a Microsoft Excel file or when you click the
Expand All
option in the summary data lineage, the
Object is not present in thecatalog or glossary
error appears.
In the AIX operating system, links do not appear for a PowerCenter resource that is on an Oracle database.
Sometimes, the lineage fails for a PowerCenter resource even when the load is successful.
Deleted objects appear in the Microsoft Excel file when the following conditions are true:
  1. You create an Oracle resource and enable the Incremental load configuration property for the resource.
  2. You load the resource.
  3. You delete one or more columns in multiple tables and delete one or more tables in the database.
  4. You load the resource and export the resource to a Microsoft Excel file.
Sometimes, the Microstrategy resource fetches the project name as the connection name instead of the valid connection name.
Lineage does not appear between a view and table in the IBM DB2 for z/OS resource if the view is in one schema and the table is in another schema.
When you load a PowerCenter resource in version 9.5.1 HotFix 3, incorrect lineage appears between a PowerCenter Source Qualifier and PowerCenter flat file source.
Sometimes, when you load a Sybase resource with complex SQL queries, the load process fails when the WL_COLUMN_DEPENDENCIES_SYBASE.S_M_ALLDB_VIEWPROC_DEPS_EXTRACT session terminates.
Lineage does not appear for a Netezza resource and PowerCenter resource if the PowerCenter resource has a SQL override that contains a "WITH" clause.
Incomplete lineage appears when you run the lineage on a custom resource.
Reloading a PowerCenter resource takes a long time to complete even when you reduce the default value of the
Source Increment Extract Window (in Days)
Linking fails for a business glossary resource and PowerCenter resource if you upload two different enumerated link files to the business glossary resource.
Incremental load
appears for Sybase, Informix, and IBM DB2 resource.
When you export lineage to a Microsoft Excel file, the
(java.lang.IllegalArgumentException: Invalid row number (1048576) outside allowable range (0..1048575)
error appears.
Metadata Manager consumes a lot of memory during lineage operation.
When purging for a resource fails, Metadata Manager purges all the resources again.

Updated June 29, 2020