When you run discovery on flat files that do not use UTF-8 encoding for character data, profiling fails and an exception appears.

You cannot view value frequency results for JSON files in the catalog.

The Lineage and Impact view breaks for a PowerCenter and Greenplum mapping. This issue occurs when you do not specify the PostgreSQL database connection type in the parameters.prm file for a mapping.

The Custom resource fails with the following error when the resource name and the delimited file name are same:

There might be chances of a security vulnerability if HTTP TRACE is not disabled for all Apache HBase ports.

You cannot filter and specify a list of resources associated with similarity discovery scanner in Enterprise Data Catalog.

Support to configure custom SSL certificates when you deploy Enterprise Data Catalog on an embedded cluster enabled for SSL.

OBIEE resource fails while ingesting metadata into the catalog.

The

Lineage

,

Impact

, or

Control

summary does not list table assets if a mapping with tables contains unconnected Lookup transformations.

Loading resources using the XMI file option in JVM parameters fails.

After you delete a custom attribute from Catalog Administrator, the search results page does not display any search result, and you cannot perform search in Enterprise Data Catalog.

Enterprise Data Catalog displays "null" as the source description value instead of the relevant source description value for an Oracle relational table in the

Overview Tab

.

You cannot view the user-defined property asset type in Enterprise Data Catalog after you create and run an Erwin resource.

For a DB2zOS resource created using PowerExchange, the objects deleted in the data source do not get updated in the catalog.

An error appears when you assign a rule to a data domain and save the data domain.

The JDBC resource fails to scan an Athena data source with external tables.

Support to run profiling on Amazon EMR 5.14 for Hive resources.

Enterprise Data Catalog displays Japanese characters as junk characters on the

Lineage and Impact

tab for a PowerCenter transformation logic.

When you scan a resource after you select the

All

option for the

Source Metadata Filter

parameter in the

Metadata Load Settings

tab for a resource, the catalog incorrectly displays metadata about external tables referred by synonyms.

The metadata scan of the Apache Atlas resource runs indefinitely.

After logging on to Enterprise Data Catalog, when you open an asset or a resource on a new tab in the browser, the

Request Forbidden

error appears on the new tab. When you close the new tab, the existing tab displays a timed out status and logs you out.

When you edit a custom attribute of business term type, Enterprise Data Catalog removes the previously assigned business term values.

Profile run fails for Hive tables when you run the profile on the Blaze engine.

In the

Relationship

tab, the relationship diagram of a resource hangs unexpectedly if you do not have the read and write permission to the related resources in Catalog Administrator.

The

Filter By

section displays a custom attribute filter option even after you delete the custom attribute in Catalog Administrator.

The profile runs on all the rows in an Amazon Redshift resource even when you choose the

First N rows

option.

The resource fails with a

NullPointerException

error if the metadata includes a newline (\n) character.

When you run a resource that contains a large number of files, the Monitoring tab becomes unresponsive. This issue occurs because multiple exceptions can appear for the resource and the Catalog Administrator takes more than 15 minutes to populate the list of exceptions.

The data domain propagation job runs continuously though a schedule is configured for the job to run only once.

After you upgrade Enterprise Data Catalog and add a new object type to an existing custom attribute, the custom attribute does not retain the object types that existed prior to the upgrade.

When you ingest data into the catalog using CSV files, there is a chance for a security vulnerability through malicious code. The vulnerability needs to be prevented.

Enterprise Data Catalog takes longer than usual to render the Lineage and Impact diagram.

Enterprise Data Catalog does not display all the columns on the

Column

tab of a table asset. This issue occurs for table asset metadata extracted from a Snowflake resource.

The IBM Datastage resource does not extract the lineage information when the data load query is in the AFTERSQL section in the SQL query.

You create and save a search tab with filter combinations, such as certified rating and resource type, or certified rating and asset type.
You navigate to the
Home
page.
You search for a random asset and the search results page appears.
You click the new search tab.

After you remove a custom attribute that has filters applied using the

Allow Filtering

option, the custom attribute incorrectly appears in the search results.

The Amazon S3 resource scan fails with a

503: Service Unavailable

error.

Sometimes, Enterprise Data Catalog displays incorrect asset name suggestions as probable matches in the

Search Results

page.

In the New Search tab page, when you create a search tab with the

Custom

option in the

Last Updated

filter section, an error appears.

If you apply EBF-13039 for a resource that was run previously and upgrade to version 10.2.2 HotFix 1, running the same resource fails after the upgrade.

When you import data domains in version 10.2.2 ServicePack 1, the

infacmd.sh tools importobjects is failing with version mismatch

error appears.

When you delete a node in a multi-node embedded cluster, the cluster fails to start and the Cluster Service does not display any log message.

No results appear for columns with DATETIME2 data type for Microsoft SQL Server resources in the catalog.

The File System resource fails to scan a Parquet file that has a Timestamp data type.

The Informatica Intelligent Cloud Services (IICS) resource fails due to proxy configuration.

Version 10.2.2 ServicePack 1 installer does not contain Microsoft Azure Blob Storage binaries.

Sometimes, incorrect ranking results appear when you search for assets in the catalog.

When the Informatica Cluster Service uses Kerberos and SSL authentication, the service stops to respond after 10 hours and the

Error 401 Authentication required

error appears.

Resource results do not appear in the catalog if the following conditions are true:

You create a resource and choose the
ALL
option in the
Metadata Load Settings
Schema
field.
You run the resource.
You run the profiling warehouse resource.

An offline resource fails to launch the Java Virtual Machine when custom JVM options are used in the resource configuration.

When you choose the

Run Similarity Profile

option and run a resource, the resource run takes multiple days to complete.

Custom resources fail after a backup and restore of the catalog as the catalog backup does not include files included with the custom resources.

Sometimes, Enterprise Data Catalog does not list custom attributes according to the ranking order in the

Search Results

page.

The Informatica Platform resource fails with a null pointer exception when a data engineering mapping has a Lookup transformation without a return port.

The

infacmd collectAppLogs

command fails with the

collectAppLogs] failed with error [Java heap space]

error message.

A user with the

Read Only

role cannot deploy Enterprise Data Catalog on a Cloudera cluster.

Column profiling fails with error:

SEVERE: [APPSDK_Msg_1762] Initialization failed with Exception: Operation CHECKACCESS failed with HTTP404 : FileNotFoundException

when you select the

Include Subdirectory

option for a resource.

A non-administrator user cannot view the value frequency for an Azure Microsoft SQL Server resource.

The Catalog Service fails to start with the following error:

ERROR [CSStartup:ConnectionHandler@162] - Unable to connect to the provided cluster URL [/api/v8/clusters/cluster/parcels/]. Make sure that you have provided valid credentials for the cluster URL.

The WANdisco Fusion verification on clusters not enabled for WANdisco Fusion caused this issue.