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:[EMAIL PROTECTED]]
>
> I remember seeing someone mention the event number to tracing
> a session to
> capture fine grained access control activity. Does anyone remember!
