RE: fgac tracing

http://www.oracleadvice.com/Tips/FGAC.htm Event 10730 (trace row level security policy predicates) can be used to dump the rewritten SQL to a trace file in the user_dump_dest. Be aware that this only happens when the cursor is reparsed. Oracle does not reparse cursors automatically from version 9.0 onwards so you must remember to execute the dbms_rls.refresh_policy procedure as the table/policy owner before enabling the trace. Set the event as normal with an alter session command:

ALTER SESSION SET EVENTS '10730 trace name context forever, level 12';

> -----Original Message-----
> From: Murali Vallath [mailto:murali_vallath_at_hotmail.com]
>
> I remember seeing someone mention the event number to tracing
> a session to
> capture fine grained access control activity. Does anyone remember!

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Jacques Kilchoer
  INET: Jacques.Kilchoer_at_quest.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).