 |
|
Oracle Tips by Burleson |
Chapter 8 General Oracle Auditing
The result of the query is not shown here, as
it’s not relevant. This action has caused auditing to be triggered.
We will see the auditing information from the trail generated.
select
client_id
from dba_audit_object
SEE CODE
DEPOT FOR FULL SCRIPT
and OBJ_NAME = 'CLAIMS'
/
CLIENT_ID
------------------
The CLIENT_ID column came back as NULL, because
by default nothing was set in the client identifier. Next, we will
issue the same query, but we will set the client identifier as
follows:
SQL> connect
appuser/*****
SQL> exec dbms_Session.set_identifier ('ARUP')
PL/SQL procedure successfully completed.
SQL> select * from claim_schema.claims;
When we query the audit trail, we find:
select client_id
from dba_audit_object
SEE CODE
DEPOT FOR FULL SCRIPT
and OBJ_NAME = 'CLAIMS'
/
The above text is
an excerpt from
the bestselling book:
Oracle
Privacy Security Auditing.
It's only $39.95 and has an
download of working security scripts:
This is the only authoritative
book on Oracle Security, Oracle Privacy, and Oracle Auditing written
by two of the world’s leading Oracle Security experts.
This indispensable book is only $39.95 and has an
download of working security scripts:
http://rampant-books.com/book_2003_2_audit.htm
|
Download your Oracle scripts now:
www.oracle-script.com
The
definitive Oracle Script collection for every Oracle professional DBA
|
|
