Search

Release Notes

Release Notes

6.4.4
- 6.5.1
- 6.5 HotFix 1
- 6.5
- 6.4.3 HotFix 1
- 6.4.3

Back Next

6.4.4 Known Limitations

6.4.4 Known Limitations

The following table describes known limitations:

Issue	Description
DA-6278	Data Archive does not send email notifications when SSL is enabled.
DA-6269	The Data Vault loader fails with the exception "Create table process failed - IDV metadata cannot be modified in parallel - Please resume the job." The error occurs when there is a data type mapping VARCHAR with 0 length to Data Vault. Workaround: Drop all of the domains that have already been created for the table using ssasql. Domain information can be found in the metadata.ddl file. Connect to ssasql and set db <archivefoldername>. Drop the domain "schemaname"."domainname" and commit. Then create appropriate mappings for the data type that created VARCHAR(0) and resume the job in the user interface.
DA-6267	If the parallel entity run option is enabled for an Informix source connection, the extractor job fails at the copy to destination step.
DA-6264	Data Vault cycle restore fails for Teradata databases.
DA-6259	During application migration on the pre-production environment, the Export Informatica Data Vault Metadata job fails when Dynamic Data Masking is enabled in the respective target connection. Workaround: When you run the Export Informatica Data Vault Metadata job, change the target connection port and host in the nucleus.ini file in the plugin path (webapp/file_archive) to the Data Vault port and host details.
DA-6240	In the preproduction to production migration job, the nucleus.ini file of the Data Archive Data Vault plugin in the production environment must be updated manually if SSL is not enabled in the preproduction environment but is enabled in the production environment.
DA-6239	The Import Informatica Data Vault Metadata job fails in the production environment if any deleted records that have not been purged exist in the pre-production environment.
DA-6075	If a Data Vault user password expires, you can update the ILM repository with a new password only if any folders have been created in Data Vault with the Create Archive Folder job.
DA-5914	Data Visualization reports do not run on the Microsoft Edge browser.
DA-5028	For Salesforce archiving, text area (rich) or HTML fields that contain an image are not archived.
DA-5027	For Salesforce archiving, creating interim tables in Salesforce is not supported if the "Namespace" prefix is configured in Salesforce. Workaround: give the interim schema as "PUBLIC" instead of "SFORCE." The "PUBLIC" value creates a table in the local database.
DA-5026	For Salesforce archiving, the primary key constraints name (PK_NAME) is not unique in different Enterprise Data Manager instances or different driver databases. Workaround: the Salesforce JDBC driver creates local database files, for example <Driver_Database>.config, <Driver_ Database>. properties, in the first instance while importing metadata. Copy those configuration files into the second instance and import metadata from the same table.
DA-5025	For Salesforce archiving, you cannot import metadata in the Enterprise Data Manager from objects with polymorphic relationships. Workaround: After you import metadata from the objects, you can create logical foreign key constraints between child and parent tables.
DA-4956	The Test JDBC Connectivity standalone job fails for Data Vault.
DA-4897	The ssacleanup utility hangs when there are too many domains in the same archive folder.
DA-4732	When you try to run existing data visualization reports, they fail if you run the reports directly from Data Visualization Designer or "Advanced Reporting" on the new SSL-enabled environment. Workaround: For Data Visualization Designer, add SSL=1 to the JDBC URL. For Advanced Reporting, first run the report from the Reports and Dashboards page or the Patient Archives, and then run the report from the Advanced Reporting interface.
DA-4035	The Data Vault Loader job fails when Dynamic Data Masking connection details are used in the target connection. Workaround: Before you run the loader, change the target connection port in the nucleus.ini file in the plugin path (webapp/file_archive).

Watch

Comments

0 COMMENTS

We’d like to hear from you! Log in to comment.