Search

Release Notes

Release Notes

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

Back Next

6.5 HF1 Known Limitations

6.5 HF1 Known Limitations

The following table describes known limitations:

Issue	Description
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-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-5914	Data Visualization reports do not run on the Microsoft Edge browser.
DA-5028	For Salesforce archiving, the 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: Provide 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 in the first instance while importing metadata. For example: <Driver_Database>.config and <Driver_ Database>. properties . 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-4897	The ssacleanup utility stops responding when there are too many domains in the same archive folder.

Version 6.5 HF1

Watch

Comments

0 COMMENTS

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