The Informatica cluster validation utility does not validate the fully qualified domain names that you specify for the gateway host, data nodes, and processing nodes.

When you rerun a resource after you upgrade to Enterprise Data Catalog version 10.5 on a multi-node cluster, duplicate objects appear in the catalog if the data source includes object ID changes.

The

generate_csr.sh

script generates the Certificate Signing Request (CSR) with a hardcoded value for the Distinguished Name (DN) in the CSR. The hardcoded value is

OU=Informatica,O=Informatica,L=RedwoodCity,S=California,C=US

.

When you upgrade to Enterprise Data Catalog version 10.5, you cannot view the custom attributes created before the upgrade for a resource and an asset.

The MongoDB and Nomad services fail and the logs display permission errors for the services when you start the services using the Informatica Cluster Service. Workaround: Perform the following steps:

Assign 757 permission to the following directories:
/usr/local/bin/mongo
/usr/local/bin/nomad
Recycle the Informatica Cluster Service.

If you run an IBM Netezza resource before copying the JDBC driver jar file to the

<INFA_HOME>/services/CatalogService/ScannerJars/externalDependencies/NetezzaScanner

directory on the Informatica cluster, the resource fails with a NullPointerException during file upload.

The Apache Solr UI does not list the collection information when the Apache Solr service is SSL enabled.

If the Informatica Cluster Service is SSL-enabled, similarity profiling backup fails when you back up the catalog using REST APIs.

The generate_certs.sh script that generates custom SSL certificates does not accept a PEM file as input. The script also does not extract all certificates in the certificate chain from the CA.

In Enterprise Data Catalog version 10.5, you lose the enrichments configured for the Tableau resource when you run the resource again.

When you create the Informatica Cluster Service using Informatica Administrator, the wizard does not validate if the gateway host name specified is a fully qualified domain name.

The infacmd backup and restore commands fail if the Informatica domain is installed on RHEL 6.x. Contact Global Customer Support to resolve the issue.

When the catalog backup fails with an

SSLHandshakeException

error, the details of the file that caused the error are not provided.

Backup of catalog using REST API fails with the following error:

org.apache.http.conn.HttpHostConnectException: Connect to

.

The

migrateContents

command fails with a

Could not connect to MRS with the provided configuration

error when you run the command on a multi-node Enterprise Data Catalog deployment.

When you download the asset change notifications to a .csv file, the file does not contain more than 20 notifications.

The disk space verification is not disabled after you configure the

IcsCustomOptions.ihs.enable.diskcheck=

custom property as false for the Informatica Cluster Service.

When you export reference objects from a Data Quality resource to a .csv file, the .csv file does not display the exported reference objects.

In a multi-node deployment, when you enable the Catalog Service, the service shows the following error:

Unable to find a valid certificate to connect to the Catalog Service

. The error occurs if you configured Informatica Cluster Service in the node that hosts the Informatica domain and the Catalog Service in a separate node.

You cannot enable Informatica Cluster Service in a multinode domain environment.

When you access Catalog Administrator using the Microsoft Internet Explorer browser, the following walkthroughs do not launch:

Resource Creation
Custom Attribute Creation
Data Domain Creation

The LDM

migrateContents

command fails in a multi-node deployment where the services are enabled for SSL.

Icons are not displayed in SSAS/SSRS/Advanced Objects [Procedure Definition].

The MongoDB service fails with the following error when you use a custom SSL certificate:

SSL peer certificate validation failed: path length constraint exceeded

. The service validation does not validate if the custom SSL certificate path length for a non-zero value.

When you use Advanced Scanners, if the Database Connection key name of a connection includes a comma, Enterprise Data Catalog does not generate a corresponding reference object.

When you upgrade from an earlier version, user-defined stop words are not migrated.

If you assign connections between a HDFS and an Informatica Platform reference resource, the connection ID appears as the schema name in the Connection Assignment page.

Enterprise Data Catalog displays incorrect source datatypes for an advanced Snowflake resource when compared to the native Snowflake resource.

When you assign the custom property

LdmCustomOptions.ingest.reindex.progress.log.level

to the Catalog Service and then add or remove any assigned custom property, the LDM.log shows the NullPointerException error.

When you configure the

LdmCustomOptions.ldm.logs.debug.packages

custom property for the Catalog Service, the debug log appears in the LDM.log file. The debug log disappears from LDM.log after you recycle the Catalog Service.

The migrateContents command fails.

Catalog backup using the REST API fails with a

java.lang.ArrayIndexOutOfBoundsException

error.

The export utility fails with the Invalid or corrupt jarfile export.jar error if you use a Java version other than version 8.

When different users are assigned as the data owner and data steward for an asset, the option to certify the asset is not available.

When viewing results in the search results page, when you use the pagination control to navigate to a different page and then apply a Resource Name filter, no results appear.

When you run relational resources such as IBM Netezza, Teradata using the external dependency approach, the resource scan fails.

Enterprise Data Catalog incorrectly displays deleted glossary child of an Axon resource in the

Contains

tab.

When you edit a custom attribute, the page takes a long time to load.

The compact view of lineage and impact diagram displays incorrect count of data elements for column level lineage.

When you access Enterprise Data Catalog using the Safari browser and launch the Introduction to Column Overview walkthrough, you cannot view a step and proceed through the flow.

Walkthroughs do not launch if the URL does not change when you navigate to the Enterprise Data Catalog home page from the search results page.

When you select a glossary that has greater than 255 characters in its name in the

Business Term Association

settings, and then run the resource, the business term association task fails for the resource and the following message appears in the log file:

java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException

.

If you run a profile on an Azure MySQL resource, Enterprise Data Catalog fails to profile columns of varchar(500) datatype.

Assets appear in a random order in the

Change Summary

tab for a resource.

When you run Amazon S3, Azure Data Lake Store, and Microsoft Azure Blob Storage resources in the high-priority mode, the source metadata and data discovery jobs fail.

The Advanced Scanners log does not report any errors although the data objects are not loaded into Enterprise Data Catalog because of model inconsistency.

The pre-validation utility does not validate Data Privacy Management services such as Elasticsearch and Spark.

X.509 role-based authorization is not supported for the MongoDB service.

For the Advanced Scanners assets, you cannot search for expressions included in calculations.

If the Snowflake resource includes a cross-database view, the view appears as Unresolved View on the

Overview

page of the resource. The System Attributes for the view displays the following error message:

ERROR Unknown table: [SNOWFLAKE]

.

For the Advanced Scanners COBOL resource, you cannot expand the linage for a multiple records file from a flat file to the field level.

When a connection is auto-assigned, Advanced Scanners displays the

Completed

status even though the connection assignment is in progress.

For a COBOL Advanced Scanners resource with connections assigned in Enterprise Data Catalog, the lineage selection for the target asset does not list all resources. Instead, lineage is displayed for all the related Enterprise Data Catalog resources.

As Advanced Scanners uses Unix operating system, you cannot establish a direct connection to the Microsoft SQL Server Reporting Services server web service. The exporter provided by Informatica is in Microsoft Windows executable format.

In the Advanced Scanners tool, you can add and edit Connection Registry entries. When performing these actions, in the

Advanced configuration

properties, you must not choose the following options as they are not supported:

edc.resourceNameSchemaMapping
edc.fileConnectionMode
edc.linkingMode
edc.resourceName