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';
SQL> select e.ename,d.dname from dept d, emp e where
14 rows selected.