Duplicate column names are allowed in the Data Vault "CREATE TABLE" statement.

Smart partitioning tables are not included in the enhanced export and import functionality in the Enterprise Data Manager.

In the Application Retirement for Healthcare Accelerator, you cannot process a payment if the AR Burndown entity contains a custom table.

Archive job from a history database fails if the WHERE clause contains a table that is not part of the entity.

Row count reports do not match between the "copy to destination" and '"loader job" steps when the retirement or archive definition has multiple entities, or when same table is present multiple times in the entity (multiple WHERE clauses).

The export function in Browse Data stores the column names in VARCHAR(4000), which truncates column names beyond 4000 characters.

When you browse data or search within a Data Vault entity, you are unable to export more than 306 records to .pdf or .csv format.

In the file archive restore list of values, the job ids are not sorted in order.

In the Enterprise Data Manager, offline import of metadata fails with a "number format exception" for Sybase sources.

The Browse Data page displays entities in the entity popup that are not in the selected archive folder.

Data Vault installation on an NFS drive fails for the AIX platform due to a Firebird limitation.