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)

Metadata Manager Fixed Limitations (10.2)

Review the Release Notes of previous releases for information about previous fixed limitations.
The following table describes fixed limitations:
In the lineage, there are no links between view and dependent tables for a Teradata resource if you have comments in the view definitions.
Metadata Manager cannot extract metadata for a Microsoft SQL Server resource that contains a schema name with a back slash (
) character.
Linking fails when you schedule a resource load in the Kerberos environment.
Sometimes, the resource load fails with the error
ORA-01461: can bind a LONG value only for insert into a LONG column
when the Metadata Manager warehouse uses Oracle database.
Metadata manager fails to load a Microsoft Analysis and Reporting Services resource during XML Metadata Interchange (XMI) parsing for some reports.
Netezza resource load fails because the session S_M_ALLDB_VIEWPROCFN_DEPS_EXTRACT_NETEZZA shuts down abruptly.
Cannot extract metadata from Sparx Enterprise Architect if you use the Universal Connectivity Framework.
Sometimes, the Metadata Manager repository contents are not restored when you run the mmRepoCmd command.
An error appears when you run the purgeMetadata command for large volumes of data in the Metadata Manager repository.
When you create a PowerCenter resource with multiple parameter files, the content of the uploaded parameter files might be incorrect.
Metadata Manager does not replace the parameters for flat file names and flat file path with actual values when you load a PowerCenter resource.
The migrateBGLinks task fails in the Kerberos environment during business glossary resource load.
When you create an URL for a custom resource and the custom resource has an attribute with LongString data type, then the character & in the URL is converted to &amp.
In the List view of the metadata catalog, when you view an object that has a forward slash character (
) in the name, Metadata Manager displays the message "Loading data…" but never displays the object.
When you create a Microsoft SQL Server resource that uses a trusted connection, testing the connection fails with a "Cannot connect to the source database" error.
Sometimes, when you create links between resources, the error
Invalid value of Tx Counter
Sometimes, the Teradata resource load fails with the stringIndexOutofBounds exception.
If you create a Tableau resource that contains multiple reports that use connections with the same name, Metadata Manager extracts only one of the connections.
When you import a scheduler after you change the scheduler name in the resource configuration file, the scheduler name remains unchanged in the Schedule tab.
Loading certain resources fails randomly with the following error in the mm.log file:
LoaderThread] ERROR TaskHandler - An error occurred in LineageGraphInternalLinksCreationTaskHandler: com.orientechnologies.orient.core.exception.ODatabaseException: Error on saving record #<number>
Workaround: Add the following properties to the file and specify property values that are less than the default values:
  • Lineage. PreCompute.ElementsInSingleTransaction. Default is 50,000.
  • Lineage. PreCompute.FetchBlockSize. Default is 5000.
When you choose a business term in the Glossary view on the Browse tab, the corresponding business glossary name does not appear in the Glossary drop down list.
Sometimes, Metadata Manager cannot display the associated object after you click the Metadata Manager asset link for a business term in the Analyst tool.
After you load a business glossary resource in a domain that uses Kerberos authentication, the load status shows
"Load Successful;Indexing Successful;Linking Failed"
instead of
"Load Successful;Indexing Successful;Not Linked."

Updated June 29, 2020