Release Notes

Release Notes

6.4.3 Known Limitations

6.4.3 Known Limitations

The following table describes known limitations:
CR
Description
IDV-413
The Data Vault utility "ssacleanup" fails for database, schema, and table names with Polish characters.
IDV-395
If a table has a grandchild table and the table names contain a period (.), the update retention job fails for a column-level policy.
IDV-353
The maximum length of a domain name in Data Vault is 128 characters.
IDV-309
When loading to Data Vault, the maximum length of a row in the .bcp file is 128,000 characters.
IDV-211
The Data Vault "ssapart" utility does not support the partition of encrypted .sct files.
DA-3511
The import index metadata job that updates index columns for Data Discovery keyword search fails when the table or column name contains a comma (",").
DA-3493
You are unable to create a report if a table has a large amount of image (BLOB) data.
DA-3445
You are unable to import custom accelerators from the
Segmentation
tab in the Enterprise Data Manager.
DA-3380
Nanoseconds data does not display in the Browse Data functionality for TIMESTAMP columns.
Workaround: To see nanoseconds in Browse Data, modify the default date format present in the system profile (
System Profile
Data Discovery Portal
Date Format Search Results)
property.
In "yyyy-MM-dd HH:mm:ss.ssssss," .s denotes the nanosecond precision.
DA-3359
Existing materialized views do not appear in the JReport web interface.
DA-3235
The reports in the Application Retirement for Healthcare Accelerator download very slowly when the dhtmljsp/docs directory is huge.
DA-3081
In the Enterprise Data Manager, only the last imported profiling results appear when you import the results using Informatica Data Quality .xml files.
DA-3080
Unique keys appear twice in the profiling results.
DA-2904
Retirement/File Archive not supported for user-defined data types of Teradata sources.

0 COMMENTS

We’d like to hear from you!