 |
|
Oracle Tips by Burleson |
Chapter 11 Oracle Fine Grained Auditing
Webserver name, among others. Since the value is
VARCHAR2, we have to store these values as a long line with some
type of delimiters between them, e.g. a pipe character. In this
case, a typical Client Identifier value looks like the following
PROLIGENCE.COM|ANAN|ws-01.proligence.com
This information is valid and useful, but it
might be more useful if these values were split into the individual
columns instead of clubbed into a single value.
Using our own auditing facility as described
earlier in this chapter, we can create columns to hold these values.
The users can call the procedure set_claim_app_ctx to set the
various attributes of the context as needed.
The procedure was described in Chapter 5, under
Virtual Private Database. It’s reproduced here.
create procedure set_claim_app_ctx
(
p_attribute_name in varchar2,
p_attribute_value in varchar2
) is
begin
dbms_session.set_context(
'claim_app_ctx',
p_attribute_name,
p_attribute_value);
end;
/
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
|
|
