Using Standard Auditing to Monitor General Activities
AUDIT SELECT UPDATE TABLE, DELETE TABLE WHENEVER NOT SUCCESSFUL;
Subsequent sections discuss the implications of your choice of auditing options and the specification of AUDIT statement clauses. A new database session picks up auditing options from the data dictionary when the session is created. These auditing options remain in force for the duration of the database connection. Setting new system or object auditing options causes all subsequent database sessions to use these options. Existing sessions continue using the audit options in place at session creation. Caution: The AUDIT statement only specifies auditing options. It does not enable auditing. To turn auditing on and control whether Oracle Database generates audit records based on the audit options currently set, set the initialization parameter AUDIT_TRAIL as described in "Enabling or Disabling the Standard Audit Trail" on page 6-13.
See Also: Oracle Database SQL Language Reference for a description
of the AUDIT statement syntax
Disabling Standard Audit Options The NOAUDIT statement turns off the audit options. Use it to reset statement and privilege audit options, and object audit options. A NOAUDIT statement that sets statement and privilege audit options can include the BY user or BY proxy option to specify a list of users to limit the scope of the statement and privilege audit options. You can use a NOAUDIT statement to disable an audit option selectively using the WHENEVER clause. If the clause is not specified, then the auditing option is disabled entirely, for both successful and unsuccessful cases. The NOAUDIT statement does not support the BY SESSION/BY ACCESS option pair. You can turn off audit options, no matter how they were turned on, by using an appropriate NOAUDIT statement. Caution: The NOAUDIT statement only specifies auditing options. It does not disable auditing. To turn auditing off and stop Oracle Database from generating audit records, set the AUDIT_TRAIL initialization parameter as described in "Enabling or Disabling the Standard Audit Trail" on page 6-13.
See Also: Oracle Database SQL Language Reference for a description
of the NOAUDIT statement syntax
Controlling the Growth and Size of the Standard Audit Trail If the audit trail is full and no more audit records can be inserted, then audited statements cannot be successfully run until you purge the audit trail. Warnings are returned to all users who issue audited statements. Therefore, you must control the growth and size of the audit trail. When auditing is enabled and audit records are being generated, the audit trail file increases according to two factors:
Configuring Auditing 6-17