First page Back Continue Last page Graphics
The SYS.AUD$ Table
Monitor for sufficient free space
- If no more free space,
- Database will reject user connections and operations
- Only SYSDBA can logon
Periodically purge
Notes:
When collecting audit records to the database (AUDIT_TRAIL=DB), make sure the SYS.AUD$ table has plenty of free space (you will learn how to monitor free space in the Tablespaces lesson; also see the supplied script FREE_SPACE.SQL for assistance). If the audit table fills up, SQL operations will fail and users will not be able to connect. Only SYSDBA connections are permitted.
So, periodically delete rows from the SYS.AUD$ table. Consider exporting or copying to a history table first.
Here is a helpful metalink document on this subject: Note:73408.1 How to Truncate, Delete, or Purge Records from Audit Trail
Warning: Oracle Metalink states that “SYS.AUD$ is the only SYS object that should ever be directly modified” See Metalink Note:73408.1.