Once you audit-enable a database, the schema required for auditing is created and the database begins looking for audit policies to implement. No generation of audit data occurs, however, until you create an audit policy (to audit the table and field events) or import the preconfigured policies, commit the changes to the database, and activate the policy.

To temporarily suspend capturing audit data, you can deactivate the audit policies. Use the disableauditing command-line option only for situations in which you want to totally and permanently disable all auditing on a database.