Metadata Manager 10.4.0
- Metadata Manager 10.4.0
- All Products
Metadata extraction using the Standalone Scanner Utility fails for the following resources when the EnableReferenceResource property is set to True:
You cannot run a profile and perform unique key inference at the same time when the following conditions are true:
After you log in to the Enterprise Data Catalog applications as a PingFederate-enabled user for single sign-on and log out, the applications prompt you for login credentials when you attempt to log in again.
Internet Explorer stops responding when you create a custom attribute and select the
Show object types in hierarchyoption from the
New Custom Attributedialog box.
Catalog Administrator may fail to respond when the following conditions are true:
The Database Scripts resource takes more than twenty hours to extract metadata using the Standalone Scanner Utility.
You can view the
Data Provisioningtab that you use to create a data provisioning task even after you delete the Informatica Intelligent Cloud Services organization from Catalog Administrator.
Sometimes, you cannot enrich the reference resources with custom attributes and business terms in Enterprise Data Catalog.
The compact view displays incorrect asset count when there are repeated assets in the origins or destinations.
In Enterprise Data Catalog, you cannot curate inferred data domain that contains structured and unstructured files from the Data Domain asset view.
When the Hadoop Gateway hostname configured for the Informatica Cluster Service is greater than 64 characters in length, the Catalog Service fails to start with the following error:
INFO security.CertificateManager - 140182417078160:error:0D07A097:asn1 encoding routines:ASN1_mbstring_ncopy:string too long:a_mbstr.c:158:maxsize=64.
Workaround: The issue occurs as the tool that generates the security certificate is not able to process common names that are more than 64 characters in length. You can configure the Subject Alternative Name in the certificate with the long name or make the common name shorter to resolve the issue.
Composite Data Domainsearch filter does not appear in the
Filter Bypanel. This issue occurs even after you configure a resource to enable composite data domain discovery and profiling.
When you upgrade Enterprise Data Catalog from version 10.2.2 HF1 to 10.4.0, the
Run onproperty in the
Metadata Load Settingstab of a Hive resource is empty.
If assets from different resources are repeated in the compact view, the view does not display all the links in the origins or destinations.
After you upgrade Informatica Enterprise Data Catalog to version 10.4.0, the Catalog takes longer than usual to open the
The Cloudera Navigator resource rescan status is not complete even after twenty hours.
The compact view displays incorrect asset count if a user without the read and write permission views the lineage and impact information in the compact view.
The scanners continue to be in an active state even after you stop the Catalog Service using Informatica Administrator.
Workaround: Stop the required YARN applications.
Enterprise Data Catalog does not retain the property values of a custom attribute of the string type in the Catalog Administrator after you add the custom attribute in the
After you run a profile with data domain discovery on a source data object, Enterprise Data Catalog displays the "?" character for UTF-8 characters in column names.
When you create a resource for Oracle Business Intelligence version12C, the
Connection Propertiessection does not display the OBIEE12C version.
Workaround: Select the
Auto Detectoption to use the OBIEE 12C version
Enterprise Data Catalog does not display internal links from a view, and extract condition objects for an Erwin resource.
When you upgrade a resource to version 10.4.0, Enterprise Data Catalog does not validate the resource configuration.
The IBM Datastage resource scan fails with the following error due to a null pointer exception:
Workaround: Set the
JVM Optionsproperty value to
-Xss10mwhen you configure the resource.
Data provisioning task fails if a table or column contains special characters in the name.
When you perform data domain discovery on the Blaze engine and the source data object has 1000 or more columns, the data domain discovery fails.
When you run a column profile with data domain discovery on the Spark engine, data domain discovery may take a long time to complete if one or more columns in the resource contain unique values.
The diagram view displays incorrect lineage information if a leaf node is indirectly linked to the seed asset.
The Lineage and Impact sliders do not work as expected after you apply lineage filters on the diagram view.
Enterprise Data Catalog does not display notifications for an Informatica Data Quality resource that is configured for
Track Data Source Changes.
The data owner, data steward and subject matter expert of a reference resource cannot certify the data elements and data objects in the resource.
Data provisioning task fails if column or field assets include spaces in the name.
If you create a data provisioning task for an Azure Data Lake Store Gen2 connection type using the
If Asset Existsoption, Enterprise Data Catalog replaces the data in delimited file instead of appending the data to the existing file.
If you create a data provisioning task for an Oracle connection type by providing the existing asset name as the target asset name in the
Create New Assetfield. Enterprise Data Catalog appends the data to the table instead of replacing the data.
You cannot view the column lineage in Enterprise Data Catalog when a flat file is used as a lookup in streaming mapping.
You cannot view inferred or curated unique keys in the exported CSV file when the following conditions are true:
You cannot search for assets using their synonyms in the Catalog. This issue occurs when you assign synonym values to asset names that are in camel case in the synonym definition file.
Opening or saving a resource in Catalog Administrator takes more time than expected.
Lineage and Impacttab does not display the lineage and impact information after you drill down the seed asset to view its child assets. This issue occurs for assets in a PowerBI resource.
In Catalog Administrator, when you enable the
Skip Unique Key Inference When Accepted or Documented Unique Key Existsproperty on the
Unique key Inference Settingsection on the
Metadata Load Settingstab you cannot skip tables that contain documented or accepted keys.
For the Microsoft Power BI resource, duplicate asset names and paths are displayed in the
Asset Lineage Summarytab in Enterprise Data Catalog.
Detailed lineage fails to open when the lineage includes more than 50,000 assets.
When you run a profile on views created in Google BigQuery that use standard SQL queries instead of legacy SQL queries, the profile run fails.
The Catalog Service fails to start if Erasure Coding is enabled for the service cluster name directory in HDFS for an existing cluster.
The Catalog Service fails to start on an embedded cluster if an incorrect Java version is installed on the node where the Catalog Service runs.
Workaround: Make sure that the Java version installed on the node is supported by Enterprise Data Catalog.