The trace files generated by setting event 10053 are usually considered some of the longest and least understandable that Oracle generates. However, they are sometimes very useful in understanding why the Cost Based Optimizer has produced what appears to be a bad execution plan and recent versions have become more readable. This presentation will give you a taste of the trace file contents and encourage you to use them when analysing SQL performance issues. - What they are and how to generate them- Why they are useful and mostly harmless- Walk-through of example trace files to highlight overall structure and useful sections- Examples of problems that you can identify using 10053 trace files”