Here is a text file created
when the database was started with the startup command:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 ??“ Production
With the Partitioning, OLAP, Data Mining
and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.1.0/db_1
System name: Linux
Node name: dw
Release: 2.6.9-55.0.2.0.1.EL
Version: #1 Mon Jun 25 14:24:38 PDT 2007
Machine: i686
Instance name: dw
Redo thread mounted by this instance: 1
Oracle process number: 44
Unix process pid: 28962, image: oracle@dw (TNS V1-V3)
Sun Aug 12 11:57:36 2007
ACTION : 'CONNECT'
DATABASE USER: '/'
PRIVILEGE : SYSDBA
CLIENT USER: oracle
CLIENT TERMINAL: pts/2
STATUS: 0
In this example, the database was started by a user connected as oracle on the host system
and connected to the instance with operating system authentication. We will cover additional
system administrator auditing issues in the next section.
Privilege Auditing
Auditing system privileges has the same basic syntax as statement auditing, except that system
privileges are specified in the sql_statement_clause instead of statements.
For example, we may wish to grant the ALTER TABLESPACE privilege to all our DBAs, but
we want to generate an audit record when this happens. The command to enable auditing on
this privilege looks similar to statement auditing:
SQL> audit alter tablespace by access whenever successful;
Audit succeeded.
Every time the ALTER TABLESPACE privilege is successfully used, a row is added to SYS.
Pages:
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552