10132 is a different from the classic two in the sense that it is is really easy for anyone to intepret, the 10132 trace event gives you a full execution plan and optimizer settings in the udump (user_dump_dest) directory.
It's an easy thing to throw in a script or even as a logon trigger when troubleshooting query problems. Think hibernate or other (weird) ORM tool.
Lets take a look:
SQL> alter session set eventsAnd the trace we get looks like this.
2 '10132 trace name context forever, level 12';
Session altered.
SQL> select e.ename,d.dname from dept d, emp e where
2 d.deptno=e.deptno;
ENAME DNAME
---------- --------------
SMITH RESEARCH
...
MILLER ACCOUNTING
14 rows selected.
SQL>
5 comments:
That's the trace without tkprof parsing?
No tkprof involved, the trace file is fairly straight forward and readable in any editor.
In 10G. The 10053 trace extended to include Y10132 at the same time.
Oracle trace events are useful for debugging the Oracle database server. The following two examples are simply to demonstrate syntax. Refer to later notes on this page for an explanation of what these particular events do sbobetaprender poker
This article is really useful I learn so much about it
Best Online Pharmacy
Post a Comment