Added support for Unicode characters. Requires the Clarify database to be unicode enabled.
If an SQL statement generated by ArchiveManager returns an error resulting in "Error in basic query" message being written to the log file, this message is now elevated to ERROR category and all information necessary for debugging: RDBMS-returned description and the SQL statement itself are also written to the log file.
Behavior Changes
In a purge/archive operation, null and default fields are not written to the export file by default. To include NULL values, and defaults (such as empty strings) in the archive file, use the -expdef option. Refer to the Purge/Archive Command Parameters topic for more information on the -expdef option.
Bug Fixes
Fixed a problem with missing objects in export file occurring when a parent object is skipped due to STOP_IF clause condition being true. For example, a directive file calls for export of cases and related contacts. Before the fix, if two cases, A and B, are related to the came contact C, and case A is exported first but skipped because of a STOP_IF clause, the common contact C would have been considered as already exported for the sake of case B. The export file would not contain the contact C information, however, causing an error on import. The fix makes sure that skipping of case A removes contact C from the list of exported objects resulting in proper export of case B and its dependent objects.
Database Platform Support
ArchiveManager version 2.3 is supported only with Microsoft SQL Server databases. Previous versions (up to 2.2.1) do support Oracle databases. It is planned that the next version of ArchiveManager will include support for Oracle. If this is a need for your organization, please contact Dovetail Software.
