Enterprise Data Catalog Fixed Limitations ( Update 1)

Transcription

1 Informatica LLC Enterprise Data Catalog Update 1 Release Notes September 2018 Copyright Informatica LLC 2015, 2018 Contents Enterprise Data Catalog Fixed Limitations ( Update 1)... 1 Enterprise Data Catalog Known Limitations ( Update 1)... 4 Enterprise Data Catalog Fixed Limitations (10.2.1)... 6 Enterprise Data Catalog Known Limitations (10.2.1)... 7 This document contains important information about fixed limitations and known limitations for Enterprise Data Catalog version Update 1. Enterprise Data Catalog Fixed Limitations ( Update 1) The following table describes the fixed limitations: Bug LDM-6619 EIC-8891 EIC-8159 EIC-8076 EIC-6288 EIC-6087 EIC-5833 When you run the profiling scanner on the File System, HDFS, Azure Data Lake Store, OneDrive, SharePoint, Microsoft Azure Blob Storage, or Amazon S3 resources, an exception appears if the file name of the data source contains quotes. When you access a relationship for an object through the REST API, an invalid JSON response is generated. If an Amazon S3 bucket contains a directory name with a forward slash (/), the Amazon S3 resource fails and the following error appears: ERROR com.infa.products.ldm.framework.scanner.execution.impl.scannertask- {RunId=b ce27-491c-ad a066f0c} {Resource=takdevlanding_2} {ScannerId=AmazonS3Scanner} A PowerCenter resource fails and the following error appears if you provide an invalid connection name: [IngestionClientException_00039] Parameter name or type is empty. Please check that these required properties are provided properly. After you run a Business Glossary resource, Enterprise Data Catalog does not display a few custom properties, such as status and phase, in the Overview tab. The UCF.ApacheHadoopHBaseNoSQLDatabase resource fails with a data validation error. This issue occurs if an incorrect profile ID is used to generate an HBase model. After you import a CSV file that contains assets with associated business terms in the catalog, Enterprise Data Catalog does not display the associated business terms in the Overview tab of the asset

2 EIC-5055 EIC-4928 EIC-4926 EIC-4900 EIC-4776 EIC-4654 EIC-4623 EIC-4621 EIC-4609 EIC-4545 EIC-4378 EIC-4202 EIC-3547 EIC-3357 EIC-2970 The UCF.CobolCopybook resource fails if you do not generate the scanner jar using the "Others" value for categoryname parameter in the scanner.properties file. The detailed lineage summary does not display a mapping if the mapping contains a lookup transformation for a PowerCenter resource. When you load a PowerCenter resource that contains a mapping with an SQL override query, the detailed lineage summary does not display the source links in the mapping. Informatica Cluster Service fails to start and the following error appears in the log file: ERROR com.infa.products.ihs.service.ambari.requestpollingthread- Ambari request to Install of the 'ZOOKEEPER' is aborted or failed. View the log files of Ambari server and Ambari client for more information. A run-time error appears in the Overview tab of an asset if the following conditions are true: 1. Add an image in the section. 2. Save the description. 3. Edit and save the section. Profiling scanner fails for a JDBC resource if the data source contains an unsupported data type. The profile validation for an Oracle resource fails with the following error: Profiling exception occured: java.lang.runtimeexception:java.lang.runtimeexception: The input Type object is null After you enable detailed lineage to configure and run an Informatica Platform resource with a target version earlier than version , the scanner runs successfully without an error but metadata is not extracted. The detailed lineage in the lineage and impact view does not display the Java code in a java transformation for a PowerCenter resource. You cannot delete multi-valued custom attribute values of reference data type in Enterprise Data Catalog. Sometimes, when you run multiple Informatica Platform resources at once, one of the Informatica Platform resource fails with the following error: Internal error. Secure communication failed because of the following SSL error: [SSLUtil_0004] The infa_truststore.jks file cannot be found. The truststore file must be in JKS format and must contain a certificate in PKCS12 format You cannot view the lineage information for flat file sources and targets of a PowerCenter resource on a Microsoft Windows machine and a File System resource. This issue occurred for a File System resource configured using the SMB/CIFS file protocol. After you create a mapping with a lookup transformation and connect a column to a table, the lineage and impact view displays incorrect summary and detailed lineage information for an Informatica Platform resource in Enterprise Data Catalog. Enterprise Data Catalog does not display lineage information if you use a Database Script resource and the script contains an INSERT ALL query. If a mapping contains an SQL or lookup transformation, Enterprise Data Catalog does not display the source qualifier and displays a source table that is not linked in the detailed lineage view for a PowerCenter resource

3 EIC EIC EIC EIC EIC-6521 EIC-7272 EIC-8155 EIC-7651 EIC-4738 EIC-6303 EIC-7638 EIC-4608 EIC-5422 The error "You do not have permission, please contact the Administrator " appears in the value frequency section of Enterprise Data Catalog when there is no value frequency data for the asset. Profile run fails if a schema name in a Microsoft SQL Server resource contains the $ character. This issue occurs if you choose column profile with a sampling option for the resource. The auto connection assignment fails for a PowerCenter resource if an object ID in the PowerCenter object contains a backslash (\). For example, "Object ID: */$PMRootDir\pfiles\NAC\$PMFolderName \/_" An Erwin resource fails with a data validation error if the resource contains multiple entries of attributes in a table, such as "com.infa.ldm.erwin.position" and "com.infa.ldm.erwin.note". The profile run for a resource fails if the resource has a table that has single quotes in the table name. When you run a Oracle resource with the incremental profiling option, the Profile Result Fetch type statistics field displays incorrect statistics. Sometimes, when you run a Salesforce resource with data domain discovery, the profile run fails and a java.util.concurrent.executionexception exception appears. Sometimes, when you run a Salesforce resource, the profile run fails and a...value is too Large exception appears. When you choose the Data Domain Discovery and Run Discovery on Source Metadata options and run a resource, the number of records in the Progress and Statistics section for the Profile Results Fetch and Profile Run jobs do not match. Sometimes, the Number of objects successfully profiled field for the Profile Run job displays 0 even when the profile run is successful. When you run the profiling scanner on a Microsoft SQL Server data object, the Invalid utf8 data error appears. Sometimes, the Erwin resource run fails with the ".. cannot have multiple entries for attribute" error. Sometimes, Enterprise Data Catalog does not display the Operation system attribute for an Initial SQL asset in the Tableau resource

4 Enterprise Data Catalog Known Limitations ( Update 1) The following table describes known limitations: Bug LDM-7044 EIC-8243 EIC-6430 EIC-6422 EIC-6274 EIC-6234 EIC-6073 EIC-5916 EIC-5783 EIC-5734 EIC EIC Sometimes, the test connection fails for an Axon resource if you do not select the Enable Secure Communication option when you create the resource. Workaround: To resolve this issue, perform one of the following tasks: - Select the Enable Secure Communication option, and then click Test Connection. - Save the resource and re-enter the password in the connection properties, and then click Test Connection. You cannot create a custom attribute with the same name as an existing system attribute. Sometimes, resources take a longer time to run when you configure multiple relational resources with auto connection assignment. When you update the Catalog Service from any previous version to version Update 1, the following error occurs: ScannerPluginRegistrationManager@288] - [ModelValidationException_00016] Datatype for Attribute [FireonUpdated] has been altered. Expected: [core.boolean]. Found: [core.integer]. For a PowerCenter and Informatica Platform resource, Enterprise Data Catalog displays the incorrect summary and detailed lineage information for a lookup transformation when the database table is not connected with the target table. When you open a Salesforce asset in Enterprise Data Catalog, the profile results for the asset does not appear in the Columns tab. Enterprise Data Catalog displays a mapping that is deleted even after you re-run the PowerCenter resource in Catalog Administrator. An Amazon S3 resource fails with the following data validation error: Error occured in scanner execution java.util.concurrent.executionexception: com.infa.products.ldm.filescanner.file.processor.api.fileprocessorexception: java.util.concurrent.executionexception: com.infa.products.ldm.filescanner.file.processor.api.fileprocessorexception: com.infa.products.ldm.ingestion.exceptions.datavalidationexception: [DataValidationException_00009] The detailed lineage summary does not display the stored procedure transformation links for a PowerCenter resource. When you run a HDFS resource on an XML file that has more than 1000 elements, the profiling run fails for the resource. Catalog Administrator does not display the connections for UCF.SAPPowerDesigner resource in the Connection Assignment page. If the resource name, application name, and parameter file share the same name, the Informatica Platform resource fails with the following error: ERROR com.infa.products.ldm.lineageservice.client.impl.lineageserviceclientimpl- Sep 14, :21:46 PM com.infa.products.ldm.scanners.mrsscanner.cmd961bundle.lineageservicecaller $LineageServiceTask disconnect

5 EIC EIC EIC EIC EIC EIC EIC EIC EIC EIC EIC EIC EIC EIC Sometimes, incremental profiling does not work as expected for a Microsoft SQL Server resource. The lineage summary does not display flat files that are present in the Window File System resource. This issue occurs when you use FTP connection type to configure the Windows File System resource. Enterprise Data Catalog incorrectly displays custom attribute value assigned to columns and synonyms in the exported file if the following conditions are true: 1. In Catalog Administrator, create a custom attribute of reference data type and assign the custom attribute to a resource and table object type. 2. When you create a resource, assign the custom attribute value to the resource, and then select the Propagate option under the custom attribute. 3. In Catalog, open the resource that you have created. 4. Click Export. 5. In the Export Custom Attributes window, select all asset types, and then select the custom attribute that have you created. 6. Click OK. For a PowerCenter resource, the missing link report displays the incorrect file path if the flat file connections are created using the default values. When you create a Azure Microsoft SQL Server resource, enable data discovery, and run the resource, the temporary tables that are created during the resource run are not deleted by default. If you use the FTP connection type for a PowerCenter, the resource does not fetch the parametrized connection name for the FTP connection. When you configure an Informatica Platform resource with an incorrect domain name, the resource fails and the scanner log file points to the lineage service log file incorrectly. When you run an HDFS resource after you run a PowerCenter resource with Auto Connection Assignment, the HDFS resource run takes a long time to complete. When you run a resource that has empty source files, the profile run fails and a null pointer exception appears in the log file. Profiling fails and the error "Failed to allocate 568 bytes error" appears if you choose the following options and run a HDFS resource: - File type is set to Microsoft Excel. - Profile Run Option field is set to Data Domain Discovery. - Select Data Domain field is set to Specify Data Domains. You choose one or more data domains. When an HDFS connection is parameterized, the connection assignment path displays the parameter value appending the path for a PowerCenter resource. The test connection fails for the UCF.MongoDBNoSQLDatabase resource and the following error appears: Error com.mongodb.mongocommandexception: Command failed with error 13: 'not authorized on admin to execute command { listdatabases: 1 }' on server inkrh65qa01: The full response is { "ok" : 0.0, "errmsg" : "not authorized on admin to execute command Sometimes, Enterprise Data Catalog displays an incorrect test connection message after you configure an Informatica platform resource with an incorrect domain name. Sometimes, the inferred data domains appear in green instead of orange in the Similar Column section in the Overview tab

6 EIC EIC An incorrect URL is generated if you provide the region name in the Amazon S3 URL. Sometimes, Enterprise Data Catalog displays the deleted business terms. Workaround: Refresh the page. Enterprise Data Catalog Fixed Limitations (10.2.1) Review the Release Notes of previous releases for information about previous fixed limitations. The following table describes fixed limitations: Bug LDM-6588 LDM-6555 LDM-6215 LDM-6109 LDM-5997 LDM-5544 EIC-3269 EIC-3152 EIC-2669 An error appears when you run an SAP R/3 resource with the First N rows sampling option. When you run the profiling scanner on a Microsoft SQL Server data object, the Invalid utf8 data error appears. When you run a Teradata resource after you choose a sampling option, the column profile results take a long time to appear. This issue occurs because Enterprise Data Catalog runs the column profile on full tables instead of a data source sample. When you run a resource with the Random sampling option, the error message SEVERE message "FAILED to fetch statistic appears in the Data Integration Service logs even when the profile run is successful. The Metadata Load Settings > Basic Profile Settings > Source Connection Name option does not display the correct tool tip. When you run a column profile on an XML data object, the data validation error appears if a column field name in the data object contains the - character. If you enable the Similarity Profile option and choose First N rows sampling option for a Microsoft SQL Server 2014 resource or Microsoft SQL Server 2016 resource that has more than 250 columns, and you run the resource on the Blaze engine, the similarity scanner fails with null pointer exception. Inconsistent profile results or value frequency results appear when you run a profile on Random N rows of a Microsoft SQL Server 2014 resource or Microsoft SQL Server 2016 resource on the Blaze engine. Similarity profile runs on all the rows in the data object even when you configure the sampling option as First N rows

7 Enterprise Data Catalog Known Limitations (10.2.1) The following table describes known limitations: Bug LDM-5217 LDM-5226 EIC-4632 LDM-5188 EIC-4015 EIC-4329 LDM-5081 LDM-5222 EIC-3288 EIC-3853 PLAT EIC-1486 LDM-3557 LDM-3735 LDM-4345 EIC-4306 You cannot terminate the scanner job if the scanner is in PauseRequested or CancelRequested state. Workaround: Kill the yarn job corresponding to scanner. If the scanner job does not display Failed state, then restart the Catalog Service. You cannot select a negative value using the slider filter for an integer custom attribute. Workaround: Configure the custom attribute to allow filter based on range. You cannot delete custom attributes in Enterprise Data Catalog if you create custom attributes using the REST API. When you search for an asset name that contains an underscore (_), the search results page does not return any result. When you run an Avro file with fixed data type, the core scanner displays the precision as undefined and the profile run fails with a null pointer exception. When you run a Netezza resource, the core scanner extracts junk tables as tables and the profiling scanner fails when it runs on the junk tables. When you delete an Informatica Axon resource, Enterprise Data Catalog does not delete the custom attribute assigned to the asset from the catalog. When you configure a user with read and write permission for one resource in the Catalog Administrator, Enterprise Data Catalog displays the total resource count instead of a count of one in the search page for the user. When a column in a data source does not contain any data, the Similarity Discovery system resource does not discover columns based on column name. When Enterprise Data Catalog performs profile validation, the profiling scanner stops to run the profile on the remaining tables if the validation fails for the first table or second table. The value frequency pane in the Assets Details view does not display minimum and maximum values for columns with Date data type. The Transformation Logic view displays inaccurate mapping names for the Informatica Cloud Services transformations. The File System resource fails with OutOfMemory error when scanning a large single JSON file. The Column profile option is incorrectly enabled for unstructured data sources. Workaround: Use Data domain discovery option or Column profile and data domain discovery option for unstructured data sources. The relationships REST API returns different levelcount details for the same query. Sometimes, Enterprise Data Catalog displays incorrect lineage information for an Informatica Platform resource if a workflow contains a mapping. Workaround: Run the resource again

8 EIC-1837 EIC-3848 LDM-6403 EIC-1835 LDM-5192 EIC-3003 LDM-5783 EIC-4559 EIC-4640 LDM-5987 EIC-2975 LDM-3912 EIC-4626 LDM-5220 EIC-4651 LDM-6668 Relationship diagram does not show synonyms. Profiling scanner does not run on Avro and Parquet files if the files are located in OneDrive, SFTP, or remote Windows location. Incorrect profile results appear when you perform data domain discovery on compressed files. In the Asset Details view of a synonym, the Contains panel displays source qualifier and mapping assets along with columns instead of just columns. For an Apache Atlas instance running on a Kerberos-enabled Hortonworks Data Platform (HDP) cluster, the Apache Atlas resource extracts source and target information only for Hive. Erwin resource does not extract metadata from tables that share the same name. Enterprise Data Catalog runs the profiling scanner only on the first 1 MB of data for a JSON data source. The scanner ignores the rest of the file. Enterprise Data Catalog does not display the lineage of a report when the connection links are not generated for the report. Enterprise Data Catalog does not add a business title to a resource if the resource name contains a locale character. Enterprise Data Catalog and Catalog Administrator display junk characters in the search results and resource properties section after you change the server locale to Japanese. Duplicate mapping objects appear in the lineage and impact view for a table linked to a mapping containing the lookup transformation. Custom metadata resource does not extract connection parameters for Business Intelligence metadata sources. An Informatica Platform resource fails if a mapping contains unstructured files, such as PDF. After you fix the incorrect details in a reusable configuration used for a resource, the changes do not take effect on the resource. After you create a PowerCenter mapping with a stored procedure transformation the connection links are missing between the stored procedure transformation and stored procedure in the database. A run-time error appears for a data domain or composite data domain if the following conditions are true: 1. You open the Catalog Administrator in Internet Explorer version You create and save a data domain or composite data domain. This issue occurs only for data domains and composite data domains that have a non-en character in their names