Purge Audit Files (ttaad4261m000)

Each time an audit sequence file exceeds its maximum size, which is specified in the Audit Trail File Sizes (ttaud3135m000) session, the sequence file is terminated and a new sequence file is generated. The maximum number of sequence files for each table/company combination is 999. When the last sequence file is terminated, the audit server tries to reuse sequence file 000 again. However, the audit server cannot overwrite existing sequence files.

Use this session to remove the old sequence files so that the audit server can reuse them to write new audit information.

Caution!

Remove audit sequence files through this session only. Do not remove audit sequence files by using commands such as rm or del. The status of the sequence file is maintained in the sequence header in the audit information file. When this session deletes the sequence file, the session also sets the status of this sequence in the information file as deleted. If the file is removed by any other means, the status is not set and this results in inconsistency.

To purge sequence files, specify a range of companies, packages, and tables. Then specify the remaining settings. See the field help.

Click Purge to remove the audit sequence files involved.

Note s

You can purge an audit file only if these conditions are met:

  • Cleaning is allowed for the audit file: that is, the Cleaning allowed check box in the Audit Trail Security (ttaud3137m000) session must be selected.
  • You are authorized to purge the audit file. See the online help of the Audit Authorizations (ttaad4162s000) session.
  • The audit file is not currently active: you cannot clean audit files with status "UNTERMINATED".
Status Aborted

During database actions, the audit server logs the actions in the audit trail. During the commit, the audit server inserts an entry in the Transaction Notification table (ttaud110). If the transaction is aborted, no entry is inserted in this table. Database actions that do not have a corresponding Transaction Notification receive the status “Aborted”.

Note

You cannot purge the last, most recent, audit sequence file as it is currently in use. When transactions in the last sequence file are purged through Purge Audit Files (ttaad4261m000) the transactions remain in the audit trail. The corresponding Transaction Notification (ttaud110) are deleted. As a result these transactions are regarded as “Aborted” transactions.

To avoid this you must force a new sequence file by stopping the current sequence:

Go to the Display Audit Sequences (ttaad4560s000) session and click Stop Sequence.

The audit server automatically starts a new sequence.

Now you can start the purge.

 

Sequence

If this check box is selected, the purge is performed based on sequence; you must specify the range of sequence files to be purged.

Note

A purge action is either based on sequence or commit time:

  • If you select the Sequence check box, the Commit Time upto and including check box is automatically cleared, and vice versa.
  • If you clear the Sequence check box, the Commit Time upto and including check box is automatically selected, and vice versa.
Commit Time upto and including

If this check box is selected, the purge is performed based on commit time.

Commit Time upto and including

Specify a commit time. All sequence files with the specified commit time, and older files, are purged.

Show Progress Bar

If this check box is selected, a progress bar is displayed during the purge process.

Force remove of transaction notifications

If this check box is selected, removal of transaction notifications is forced. Transaction notifications for tables without audit trail host, or without info file, are removed.

 

Purge

Starts the purge process.