Incorrect report count appears for a MicroStrategy resource when the following conditions are true:

You run a MicroStrategy resource in version 10.2.1 or version 10.2.1 Service Pack 1.
You upgrade to version 10.2.2 HotFix 1.
You re-run the resource.

In Enterprise Data Catalog, the

Allow Sorting

and

Allow Filtering

options are not enabled for some system attributes, such as location.

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.

Incorrect results appear in the catalog when you search for a synonym.

In Catalog Administrator, you can view the

Data Provisioning

tab for all the resources including Oracle and Microsoft SQL Server resources.

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 delete a node in a multi-node embedded cluster, the cluster fails to start and the Cluster Service does not display any log message.

When you create and run an IBM DB2 with z/OS resource with the

Source Metadata Filter

option, the scanner results are incorrect in the catalog.

During Catalog Service backup and restore operations, sometimes, the restore operation fails with the

[Failed after attempts=40, exceptions:

error.

Catalog Service does not start if you enable erasure coding in the HDFS cluster.

Data discovery fails for a text file with file size exceeding 1 GB or a Microsoft Excel file with file size exceeding 200MB when the

Maximum Heap Size

option for the pmdtm process in Informatica Administrator is set to the default value.

When you run a resource in the File Management resource group, the resource run fails if the resource has a Microsoft Excel file with the file size exceeding 200 MB.

In the Enterprise Data Catalog Plug-in, when you search for assets without a title or description field qualifier, the search results display only those assets that have the search string in the asset names.

The search results for classes, attributes, and mappings appear under incorrect and unclear labels for SAP HANA, PowerCenter, IBM InfoSphere DataStage, and Informatica Platform resources.

When you run an SAP HANA resource with a calculation view that has a SQL condition, the catalog displays an additional empty asset for the resource.

The following issues appear when you configure the

LdmCustomOptions.ingest.hbase.namespace.name

namespace with a value other than

ldmns

:

The "userConfigurationStore" and "userWatchStore" parameters in the connection utility use the default namespace ldmns instead of the configured namespace value.
During Catalog Service backup and restore operations, the service does not take a backup of the configured namespace.

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

When you run a SAP HANA resource with the calculation view of star join or complex type, the following issues appear:

When the cluster does not have appropriate privileges, backup and restore of Catalog Service fails with the

[java.lang.IndexOutOfBoundsException: Index: 0, Size: 0

error.

When you fetch a custom attribute using the REST API, the

Validation Failure

error appears if the pageSize parameter of the custom attribute exceeds 10,000.

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.

In the Developer tool or Analyst tool, if you import a table twice and run profiles on the imported tables, the profiling warehouse scanner migrates the profile results only for the table with the original table name.

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.

In Informatica Administrator, when you start the Catalog Service on Solr, the

java.net.BindException: Address already in use

error message appears.

When you pause and resume a Custom scanner, duplicate jobs appear in the

Monitoring

Statistics

section in Catalog Administrator.