A non-administrator user can scan the profiling warehouse associated with Informatica Data Quality resource.

After you deleted the associated data owner, data steward, and subject matter expert from the Enterprise Data Catalog Discovery, Data Asset Analytics does not display the delete time in the reports.

After you disable the resource scheduler for the Data Domain and Data Domain Propagation resources, the Catalog Service restart enables the scheduler for the resources.

After you export data domains from Enterprise Data Catalog, the export file incorrectly displays rejected data domains in the

DataDomains Accepted

column.

An internal error occurs when you export synonyms and public synonyms to a TDE file irrespective of the permissions and privileges assigned to you.

Auto connection assignment between SAP BW and SAP S/4HANA resources fails.

Data Asset Analytics displays incorrect active users count in the

User Adoption

dashboard tab. This issue occurs if users from different security domains share the same name and include the security domain column in

User searches

report.

Data Asset Analytics does not display special and multi-byte characters as expected in the

User

login drop-down list.

Enabling the Catalog Service fails when the Informatica Cluster Service host name is longer than 64 characters.

Enterprise Data Catalog displays incorrect source position for the columns from a schema table and synonym asset types.

Enterprise Data Catalog does not display the minimum and maximum frequency value results if an Athena data source columns contain Decimal datatype.

For operating system profile, the JDBC resource fails to import metadata from an Athena data source into Enterprise Data Catalog.

If you override the path of the target, the Informatica Cloud Service resource does not extract the targets created at run time for data sources such as Microsoft Azure Blob Storage, and Azure Data Lake Store Gen2

If you select a password protected package, the metadata scan of a File type SSIS resource fails.

In Data Asset Analytics, the asset enrichment data appears as duplicate whereas the enrichments come from different resources.

Purging a resource takes a longer duration compared to purging a resource in version 10.4.0. This is due to additional consistency checks performed to improve catalog stability.

The

Scan History

window does not display the complete list of source change details.

The JDBC resource fails to scan an Athena data source that contains views.

The SAP S/4HANA resource does not extract metadata from the SAP S/4HANA application components and packages if the application components and packages have the same name.

The SAP S/4HANA resource does not extract views appended to a ABAP Core Data Services (CDS) view in the Catalog.

The additional consistency checks that are added to improve the Catalog stability increases the time consumed by the resource purge operation.

The asset type of a Query element is incorrectly populated in the

Lineage and Impact

tab for SAP BW and SAP BW/4HANA resources.

The data provisioning task fails for the following source connections:

Amazon S3
Azure Data Warehouse
Teradata
JDBC Oracle
Amazon Redshift
Azure Blob
Salesforce

The data provisioning task fails for the following target connections:

Amazon S3
Azure Data Warehouse
Teradata
JDBC Oracle
QlikView

The profile run fails on the Spark engine if the source column name contains special characters.

The rejected data domains still appear in the inferred state even after you delete the rejected data domains from the import file during the asset data import.

When you view the lineage for a MicroStrategy resource from the grid layout, the source or the target data set is linked to itself.

You cannot export the asset data to a TDE file if the asset name is in lower case. This issue occurs if you export using the JDBC connection type.

You cannot filter by user name in the

User Login Name

filter option if the user name consists of a single quote character.

You cannot view sections such as Questions, Reviews, and Ratings for a Process Definition in the Catalog.

You cannot view the

Scan History

window if there is one source change for a resource on the

Change Summary

page.

You cannot view the profiling source changes of assets after you apply the

Asset Type

filter option on the

Change Summary

page.

For an Amazon S3 resource, the profile run fails on the Parquet file that contains dot (.) in the field name.