Table of Contents

Search

  1. Abstract
  2. Installation and Upgrade
  3. 10.1.1 HotFix 1 Fixed Limitations and Closed Enhancements
  4. 10.1.1 HotFix 1 Known Limitations
  5. 10.1.1 Update 2 Fixed Limitations and Closed Enhancements
  6. 10.1.1 Update 2 Known Limitations
  7. 10.1.1 Update 1 Fixed Limitations and Closed Enhancements
  8. 10.1.1 Update 1 Known Limitations
  9. 10.1.1 Fixed Limitations and Closed Enhancements
  10. 10.1.1 Known Limitations
  11. Informatica Global Customer Support

Metadata Manager Known Limitations (10.1.1)

Metadata Manager Known Limitations (10.1.1)

The following table describes known limitations:
Bug
Description
MM-2722
On Solaris, creating an Informatica Platform resource that extracts metadata from a version 10.1.1 deployed application fails with the following errors in the mm.log file:
ERROR InfacmdUtil - Invalid Platform
ERROR ResourceUtil - The resource configuration properties are not valid. Check the mm.log file for details.
MM-2709
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.
Workaround: View the object in the Tree view of the metadata catalog.
MM-2707
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.
MM-2678
The default Metadata Manager Agent that starts when the Metadata Manager Service is enabled does not work when the domain uses Kerberos authentication.
Workaround: Download and install the Metadata Manager Agent separately on a Windows machine.
MM-2663
If you associate a business term with an object that has any of the following special characters in the name, and then you remove the term association, the Analyst tool glossary still shows the object as a related object for the term:
< > = / \ [
MM-2344
When you load an Informatica Platform resource that contains a mapping with an SQL override, Metadata Manager does not parse the SQL query or generate the links associated with the query.
MM-2320
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.
Workaround: Use automatic connection assignments for linking. When you use automatic connection assignments, Metadata Manager creates links for all connections.
MM-2312
When you load a Cloudera Navigator resource incrementally, Metadata Manager does not extract new Sqoop job templates and executions.
Workaround: Disable incremental loading.
MM-2295
When you load an Informatica Platform resource that uses a parameter to specify the file name or path of a flat file, Metadata Manager does not resolve the parameter.
MM-2291
If you link a business glossary term to a catalog object that has any of the following special characters in the name, the Analyst tool glossary does not show the object as a related object for the business term:
~ ` ! @ # $ % ^ & * ( ) - _ = } { [ ] | \ ; : ' " , < . > ? /
MM-2283
You cannot create a Microsoft SQL Server Integration Services 2014 file-based resource using the File configuration property if the package file also has dependent connection manager (.conmgr) files.
Workaround: Put the package file and all related connection manager files in the same directory, and specify the Directory configuration property instead of the File configuration property.
MM-2227
When you load an Informatica Platform resource that uses a parameter to specify the schema name of a lookup table, Metadata Manager does not resolve the parameter.
MM-2074
When you run the rmu command line program on a resource from a previous version of Metadata Manager, migration fails. For example, migration fails if you run rmu version 10.1 on a 9.6.1 HotFix 4 resource that has not been upgraded to 10.1 and marked deprecated by the upgrade process. (461099)
MM-2064
When you load an Oracle resource incrementally, the mm.log file shows some "unique constraint" transformation errors. (460309)
MM-2026
You cannot load an Informatica Platform resource that extracts metadata from a deployed application of version 9.5.1 or any 9.5.1 HotFix.
Workaround: Extract metadata from an application archive file. (457381)
MM-1853
When you use the rmu migration utility to migrate a 9.5.1 HotFix 2 resource, the migration fails with the following errors:
ERROR - Unrecognized option: -includePassword ERROR - Migration for resource:Resource Type-<Type>, Source System Version-<Version>, name-<Name> failed
Workaround: Upgrade the Metadata Manager warehouse to version 10.0, and then migrate the deprecated resources. (442395)
MM-1848
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 imm.properties 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.
(441925)
MM-1846
When the Metadata Manager repository database type is Microsoft SQL Server, and you create a Metadata Manager Service with secure JDBC parameters in the database connection URL, the service cannot connect to the database.
Workaround: Enclose the secure JDBC parameters string in quotation marks.
(441860)
MM-1730
Data lineage for custom objects with "Any Model, Any Class" class-level relationships is incorrect when the objects are linked to PowerCenter mappings. (426995)
MM-1506
The
Find
button in the lineage diagram does not display search results the first time that you click it.
Workaround: Click the button a second time to display the search results. (395899)
BG-1134
When you load a business glossary resource that contains a business term with a rule asset and related assets from Metadata Manager, the Metadata Manager Service does not synchronize the related catalog objects in Metadata Manager with the related assets in the Analyst tool. The load log displays the following error:
BG links migration failed... The requested object does not exist in the catalog.
Workaround: To synchronize the related catalog objects with the related assets, unassign the rule asset from the term before you load the glossary. Reassign the rule asset to the term after the load completes. (442486)
BG-1131
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."
(441322)
BG-1127
When you load a Business Glossary resource that contains term names with backslash characters (\), the load fails with the following error: Incomplete values at line <number>
(439498)
BG-1111
When you load a Business Glossary resource that contains different combinations of special characters in the glossary name, the load might fail with an internal error or a Java runtime exception. (420072)
BG-1099
In Metadata Manager, if the name of a related catalog object for a business term contains a space as the first character, the corresponding data assets are not updated in the Analyst tool business glossary. Also, if the name of a related catalog object for a business term contains any of the following characters, the URL in the Analyst tool business glossary does not work:
` ~ ! @ # $ % ^ & * ( ) , / \ "
(393548)
BDM-2626
Metadata Manager does not support metadata extraction for dynamic mappings. (432827)