Click the Truncate button to truncate the transaction log. Doing so forces a full hot catalog backup the next time any schedule of the catalog backup policy is due.

Without a full hot catalog backup, a gap would exist in the transaction logs due to the truncation and an error during catalog recovery would occur.

If the next scheduled hot catalog backup is a differential incremental, a backup of all of the relational database files is included.

Temporary Directory For Truncation

Use the Browse button to select a directory for temporary storage during the transaction log truncation process. Make sure that enough space is available for a copy of the existing transaction log before it is truncated.

After the transaction log is successfully copied and truncated, the temporary copy is deleted.

More Information