|Oracle9i SQL Reference
Release 2 (9.2)
Part Number A96540-02
NOAUDIT statement to stop auditing previously enabled by 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.
AUDIT for more information on auditing
To stop auditing of SQL statements, you must have the
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
ANY system privilege. In addition, if the object you chose for auditing is a directory, then even if you created it, you must have the
ANY system privilege.
sql_statement_clause to stop auditing of a particular SQL statement.
statement_option, specify the statement option for which auditing is to be stopped.
ALL to stop auditing of all statement options currently being audited.
system_privilege, specify the system privilege for which auditing is to be stopped.
Table 17-1 for a list of the system privileges and the statements they authorize
PRIVILEGES to stop auditing of all system privileges currently being audited.
auditing_by_clause to stop auditing only those SQL statements issued by particular users. If you omit this clause, then Oracle stops auditing all users' statements.
userto stop auditing only for SQL statements issued by the specified users in their subsequent sessions. If you omit this clause, then Oracle stops auditing for all users' statements, except for the situation described for
proxyto stop auditing only for the SQL statements issued by the specified proxy, on behalf of a specific user or any user.
schema_object_clause to stop auditing of a particular database object.
object_option, specify the type of operation for which auditing is to be stopped on the object specified in the
Table 12-3 for a list of these options
ALL as a shortcut equivalent to specifying all object options applicable for the type of object.
auditing_on_clause lets you specify the particular schema object for which auditing is to be stopped.
schema, then Oracle assumes the object is in your own schema.
AUDIT for information on auditing specific schema objects
DIRECTORYclause lets you specify the name of the directory on which auditing is to be stopped.
DEFAULTto remove the specified object options as default object options for subsequently created objects.
SUCCESSFUL to stop auditing only for SQL statements and operations on schema objects that complete successfully.
SUCCESSFUL to stop auditing only for statements and operations that result in Oracle errors.
If you omit this clause, then Oracle stops auditing for all statements or operations, regardless of success or failure.
If you have chosen auditing for every SQL statement that creates or drops a role, then you can stop auditing of such statements by issuing the following statement:
If you have chosen auditing for any statement that queries or updates any table issued by the users
oe, then you can stop auditing for queries by
hr by issuing the following statement:
The preceding statement stops auditing only queries by
hr, so Oracle continues to audit queries and updates by
oe as well as updates by
To stop auditing on all statements that are authorized by
TABLE system privilege, issue the following statement:
If you have chosen auditing for every SQL statement that queries the
employees table in the schema
hr, then you can stop auditing for such queries by issuing the following statement:
You can stop auditing for queries that complete successfully by issuing the following statement:
This statement stops auditing only for successful queries. Oracle continues to audit queries resulting in Oracle errors.