top of page

Oracle 10053 SQL Trace Viewer

  • Writer: kyle Hailey
    kyle Hailey
  • Jul 26, 2010
  • 1 min read

The infamous 10053 trace is probably the most extensive trace for understanding why the Oracle optimizer chose a query’s execution path (also see event 10132 at level 1). The 10053 trace can been large, cumbersome and tedious to read. Finally help is on the way. See Jonathan Lewis’ blog at

(rename and take the “.doc” extension off)

 
 
 

Comments


Kyle Hailey

  • Facebook
  • Twitter
  • LinkedIn
  • Instagram

San Franisco, Ca 94131

415-341-3430  (please text initially before calling)

bottom of page