NOAUDIT

Purpose

Use the NOAUDIT statement to stop auditing previously enabled by the AUDIT statement.

The NOAUDIT statement must have the same syntax as the previous AUDIT statement. Further, it reverses the effects only of that particular statement.For example, suppose one AUDIT statement (statement A) enables auditing for a specific user. A second (statement B) enables auditing for all users. A NOAUDIT statement to disable auditing for all users (statement C) reverses statement B. However, statement C leaves statement A in effect and continues to audit the user that statement A specified.

See Also: AUDIT for more information on auditing

Prerequisites

To stop auditing of SQL statements, you must have the AUDIT SYSTEM system privilege.

To stop auditing of schema objects, you must be the owner of the object on which you stop auditing or you must have the AUDIT ANY system privilege. In addition, if the object you chose for auditing is a directory, even if you created it, you must have the AUDIT ANY system privilege.

Syntax

sql_statement_clause::=

auditing_by_clause::=

schema_object_clause::=

auditing_on_clause::=

Keywords and Parameters

sql_statement_clause

statement_option	Specify the statement option for which auditing is to be stopped. See Also: Table 8-1 Table 8-2 and for a list of the statement options and the SQL statements they audit
ALL	Specify ALL to stop auditing of all statement options currently being audited.
system_privilege	Specify the system privilege for which auditing is to be stopped. See Also: Table 11-1 for a list of the system privileges and the statements they authorize
ALL PRIVILEGES	Specify ALL PRIVILEGES to stop auditing of all system privileges currently being audited.
auditing_by_clause	Use the auditing_by_clause to stop auditing only those SQL statements issued by particular users. If you omit this clause, Oracle stops auditing all users' statements.
	BY user	Specify BY user to stop auditing only for SQL statements issued by the specified users in their subsequent sessions. If you omit this clause, Oracle stops auditing for all users' statements, except for the situation described for WHENEVER SUCCESSFUL.
	BY proxy'	Specify BY proxy to stop auditing only for the SQL statements issued by the specified proxy, on behalf of a specific user or any user.

schema_object_clause

object_option	Specify the type of operation for which auditing is to be stopped on the object specified in the ON clause. See Also: Table 8-3 for a list of these options
ALL	Specify ALL as a shortcut equivalent to specifying all object options applicable for the type of object.
auditing_on_clause	The auditing_on_clause lets you specify the particular schema object for which auditing is to be stopped.
	object	Specify the object name of a table, view, sequence, stored procedure, function, or package, snapshot, or library. If you do not qualify object with schema, Oracle assumes the object is in your own schema. See Also: AUDIT for information on auditing specific schema objects
	DIRECTORY directory_name	The DIRECTORY clause lets you specify the name of the directory on which auditing is to be stopped.
	DEFAULT	Specify DEFAULT to remove the specified object options as default object options for subsequently created objects.
WHENEVER [NOT] SUCCESSFUL	Specify WHENEVER SUCCESSFUL to stop auditing only for SQL statements and operations on schema objects that complete successfully.
	Specify NOT to stop auditing only for statements and operations that result in Oracle errors.
	If you omit this clause, Oracle stops auditing for all statements or operations, regardless of success or failure.

Examples

Stop Auditing of SQL Statements Related to Roles Example

If you have chosen auditing for every SQL statement that creates or drops a role, you can stop auditing of such statements by issuing the following statement:

NOAUDIT ROLE; 

Stop Auditing of Updates or Queries on Objects Owned by a Particular User Example

If you have chosen auditing for any statement that queries or updates any table issued by the users scott and blake, you can stop auditing for scott's queries by issuing the following statement:

NOAUDIT SELECT TABLE BY scott; 

The above statement stops auditing only scott's queries, so Oracle continues to audit blake's queries and updates as well as scott's updates.

Stop Auditing of Statements Authorized by a Particular Object Privilege Example

To stop auditing on all statements that are authorized by DELETE ANY TABLE system privilege, issue the following statement:

NOAUDIT DELETE ANY TABLE;

Stop Auditing of Queries on a Particular Object Example

If you have chosen auditing for every SQL statement that queries the emp table in the schema scott, you can stop auditing for such queries by issuing the following statement:

NOAUDIT SELECT 
   ON scott.emp; 

Stop Auditing of Queries that Complete Successfully Example

You can stop auditing for queries that complete successfully by issuing the following statement:

NOAUDIT SELECT 
   ON scott.emp
   WHENEVER SUCCESSFUL; 

This statement stops auditing only for successful queries. Oracle continues to audit queries resulting in Oracle errors.