Release Notes

Release Notes

6.4.4 Fixed Limitations

6.4.4 Fixed Limitations

Review the Release Notes of previous releases for information about previous fixed limitations.
The following table describes fixed limitations:
Issue
Description
DA-6194
If the "LEGALHOLD_GROUP_NAMES" column of the "XA_ER_ENTITY_REPORT" table has a length of 4000, the purge expired records job fails at the "generate report" step.
DA-6192
For Oracle tables that have an XMLTYPE field, the retirement job fails with a "PGA memory used by the instance exceeds PGA_AGGREGATE_LIMIT" error.
DA-6134
Security vulnerabilities require an Apache Tomcat upgrade from version 7.0.70 to 7.0.82.
DA-6069
The healthcare radiology report fails if EXAM_ID has alphanumeric characters.
DA-5949
Because of insufficient privileges, you are unable to publish reports from Data Visualization Designer after an upgrade.
DA-5911
The ssapart utility required support for materialized views.
DA-5854
A join query on two tables with "distinct count()" in the projection list throws the error "Invalid CheckSum of readed data."
DA-5823
Microsoft SQL Server, Oracle, IBM DB2, and Sybase databases require updated DataDirect JDBC drivers.
DA-5819
The ssapart utility requires support for external storage.
DA-5818
The ssapart utility requires support for encrypted SCT files.
DA-5814
The ssaserver is crashes with the error "Too Many embedded SQL" for larger SQL queries.
DA-5546
You are unable to view objects and tables in the DGA dashboard.
DA-5517
When THREADS > 10 in the QUERY section of the ssa.ini file, queries on a table with SCT files located on EMC S3 and with 1 million records in single a SCT file returns a "Forbidden 403" error.
DA-5308
The Create Indexes in Data Vault job fails when SCT files are encrypted.
DA-5074
If the number of legal holds at the table or row level exceeds the maximum limit, the table might become inaccessible with the error "Invalid LEGALHOLD serialization stream." The maximum allowed limit at table level is 256 and at row level is 32.
DA-5072
The export and import jobs in the application migration process fail when SSL is enabled.
Workaround: Before you use the application migration process, update the Data Vault Data Archive plugin. Pre-pend the odbc32 directory, where 32-bit SSL modules reside, to the LD_LIBRARY_PATH/LIBPATH.
For example: LD_LIBRARY_PATH=$1/webapp/file_archive/odbc:$1/webapp/file_archive$1/webapp/file_archive/ odbc32:$LD_LIBRARY_PATH LIB_PATH=$1/webapp/file_archive/odbc:$1/webapp/file_archive/odbc32:$LIB_PATH
DA-5029
Salesforce archiving: The currency data type value will be rounded off if it is created with high range precision.

0 COMMENTS

We’d like to hear from you!