This section describes the
NOAUDIT statement for traditional auditing, which is the same auditing functionality used in releases earlier than Oracle Database 12c.
Beginning with Oracle Database 12c, Oracle introduces unified auditing, which provides a full set of enhanced auditing features. For backward compatibility, traditional auditing is still supported. However, Oracle recommends that you plan the migration of your existing audit settings to the new unified audit policy syntax. For new audit requirements, Oracle recommends that you use the new unified auditing. Traditional auditing may be desupported in a future major release.
See Also:NOAUDIT (Unified Auditing) for a description of the
NOAUDITstatement for unified auditing
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 A enables auditing for a specific user. A second statement B enables auditing for all users. A
NOAUDIT statement C to disable auditing for all users reverses statement B. However, statement C leaves statement A in effect and continues to audit the user that statement A specified.
See Also:AUDIT (Traditional 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.
To specify the
CONTAINER clause, you must be connected to a multitenant container database (CDB). To specify
ALL, the current container must be the root and you must have the commonly granted
SYSTEM privilege in order to stop auditing for the issuances of a SQL statement, or the commonly granted
ANY privilege in order to stop auditing for the operations on a schema object. To specify
CURRENT, the current container must be a pluggable database (PDB) and you must have the locally granted
SYSTEM privilege in order to stop auditing the issuances of a SQL statement, or the locally granted
ANY privilege in order to stop auditing operations on a schema object.
audit_operation_clause to stop auditing of a particular SQL statement.
sql_statement_shortcut, specify the shortcut for the SQL statements for which auditing is to be stopped. Refer to Table 13-1 and Table 13-2 for a list of the SQL statement shortcuts and the SQL statements they audit.
ALL to stop auditing of all statement options currently being audited because of an earlier
... statement. You cannot use this clause to reverse an earlier
system_privilege, specify the system privilege for which auditing is to be stopped. Refer to Table 18-1 for a list of the system privileges and the statements they authorize.
auditing_by_clause to stop auditing only for SQL statements issued by the specified users in their subsequent sessions. If you omit this clause, then Oracle Database stops auditing for all users' statements, except for the situation described for
audit_schema_object_clause to stop auditing of a particular database object.
sql_operation, specify the type of operation for which auditing is to be stopped on the object specified in the
ON clause. Refer to Table 13-3 for a list of these options.
For object, specify the object name of a table, view, sequence, stored procedure, function, or package, materialized view, or library. If you do not qualify
schema, then Oracle Database assumes the object is in your own schema. Refer to AUDIT (Traditional Auditing) for information on auditing specific schema objects.
DIRECTORY clause lets you specify the name of the directory on which auditing is to be stopped.
PROFILE clause lets you specify the SQL translation profile on which auditing is to be stopped.
DEFAULT to remove the specified object options as default object options for subsequently created objects.
SUCCESSFUL to stop auditing only for SQL statements and operations that result in Oracle Database errors.
If you omit this clause, then the database stops auditing for all statements or operations, regardless of success or failure.
CONTAINER clause to specify the scope of the
CURRENT to stop auditing in the PDB to which you are connected. If you specify the
user must be a common user or local user in the current PDB. If you specify the
auditing_on_clause, then the objects must be local objects in the current PDB.
ALL to stop auditing across the entire CDB. If you specify the
user must be a common user. If you do not specify the
auditing_by_clause, then auditing is stopped for all common users and all local users in each PDB. If you specify the
auditing_on_clause, then the objects must be common objects.
If you omit this clause, then
CURRENT is the default.
Stop Auditing of SQL Statements Related to Roles: Example 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:
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
oe, then you can stop auditing for queries by
hr by issuing the following statement:
NOAUDIT SELECT TABLE BY hr;
The preceding statement stops auditing only queries by
hr, so the database continues to audit queries and updates by
oe as well as updates by
Stop Auditing of Statements Authorized by a Particular Object Privilege: Example To stop auditing on all statements that are authorized by
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
employees table in the schema
hr, then you can stop auditing for such queries by issuing the following statement:
NOAUDIT SELECT ON hr.employees;
NOAUDIT SELECT ON hr.employees WHENEVER SUCCESSFUL;
This statement stops auditing only for successful queries. Oracle Database continues to audit queries resulting in Oracle Database errors.