AUD$.
Special auditing is available for system administrators who use the SYSDBA and SYSOPER
privileges or connect with the SYS user. To enable this extra level of auditing, set the initialization
parameter AUDIT_SYS_OPERATIONS to TRUE. The audit records are sent to the same location as
the operating system audit records; therefore, this location is operating system dependent. All SQL
statements executed while using one of these privileges, as well as any SQL statements executed
as the user SYS, are sent to the operating system audit location.
Chapter 9: Database Security and Auditing 337
Schema Object Auditing
Auditing access to various schema objects looks similar to statement and privilege auditing:
AUDIT schema_object_clause BY {SESSION | ACCESS}
WHENEVER [NOT] SUCCESSFUL;
The schema_object_clause specifies a type of object access and the object being accessed.
Fourteen different types of operations on specific objects can be audited; they are listed in
Table 9-19.
If we wish to audit all insert and update commands on the HR.JOBS table, regardless of who
is doing the update, and every time the action occurs, we can use the audit command as follows:
SQL> audit insert, update on hr.jobs by access whenever successful;
Audit successful.
The user KSHELTON decides to add two new rows to the HR.JOBS table:
SQL> insert into hr.jobs (job_id, job_title, min_salary, max_salary)
2 values ('IN_CFO','Internet Chief Fun Officer', 7500, 50000);
1 row created.
Pages:
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553