SQL>AUDIT DROP ANY TABLE BY scott BY SESSION WHENEVER SUCCESSFUL;
What is the effect of this command?
A.
One audit record is created for every successful DROP TABLE command executed in the session of
SCOTT
B.
One audit record is generated for the session when SCOTT grants the DROP ANY TABLE privilege
to other users
C.
One audit record is created for the whole session if user SCOTT successfully drops one or more
tables in his session
D.
One audit record is created for every session of any other user in which a table owned by SCOTT is
dropped successfully
E.
One audit record is created for every successful DROP TABLE command executed by any user to
drop tables owned by SCOTT
To choose auditing for every statement that successfully creates, alters, drops, or sets a role, issue the following statement:
AUDIT ROLE
WHENEVER SUCCESSFUL;
In earlier releases, BY SESSION caused the database to write a single record for all SQL statements or operations of the same type executed on the same schema objects in the same session. Beginning with this release of Oracle Database, both BY SESSION and BY ACCESS cause Oracle Database to write one audit record for each audited statement and operation. BY SESSION continues to populate different values to the audit trail compared with BY ACCESS.
BY SESSION writes different values to the (one) audit trail
By default, auditing is set BY ACCESS.
Each time the system privileges audited exercise will generate an audit record.
BY SESSION clause to choose to use these records to form a group, so that each session is generated only one record.
(Thus, if a user were issue multiple update statements on another user, only one audit would record collection.)
BY SESSION clause to restrict the use of the audit because of the permissions on system performance and to optimize storage .