The other method uses the alter session command to generate a plain-text trace file containing
much of the information from the previous query. Here are the commands to set up tracing:
SQL> begin
2 dbms_rls.refresh_policy;
3 end;
PL/SQL procedure successfully completed.
SQL> alter session set events '10730 trace name context forever, level 12';
Session altered.
Event 10730 is defined for tracing RLS policy predicates. Other common events that can be
traced are 10029 and 10030 for session logon/logoff, 10710 to trace bitmap index access, and
10253 for simulating write errors to the redo log, among others. Once the session is altered, the
user DGRANT runs his query:
SQL> select employee_id, first_name, last_name,
2 email, job_id, salary, manager_id from hr.employees;
EMPLOYEE_ID FIRST_NAME LAST_NAME EMAIL JOB_ID SALARY MANAGER_ID
----------- ----------- ----------- ---------- ---------- ------- ----------
199 Douglas Grant DGRANT SH_CLERK 2600 124
1 row selected.
330 Oracle Database 11g DBA Handbook
Here??™s a look at the bottom part of the trace file located in the directory specified by the
initialization parameter USER_DUMP_DEST (DIAGNOSTIC_DEST in Oracle Database 11g):
Trace file
/u01/app/oracle/diag/rdbms/dw/dw/trace/dw_ora_31128.trc
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.
Pages:
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543