Toad’s “Trace File Browser” (included in the optional DB Admin Module) has been around for a number of years – yet it remains as one of the most useful and stunningly underutilized features. While numerous DBA’s and developers subscribe to the popular “Method-R” tuning approach (i.e. Cary Millsap, Method-R Corp. – and before that Hotsos) which by definition means capturing and examining Oracle trace files, shockingly most don’t leverage Toad’s Trace File Browser to make such work much easier. Some rely on Oracle’s old command line utility TKPROF along with a text editor, some use Toad’s TKPROF wizard, and some buy the Hotsos or Method-R Corp. profilers. But why suffer with old, limited command line tools or purchase more third party tools when Toad offers an awesome solution? Dan Hotka (Oracle ACE Director) and I have written many blogs on using Toad’s Trace File Browser for such tuning and wait analysis.
Now Toad 12.1, releasing Sept 19th 2013, adds a powerful and convenient new feature to the Trace File Browser – automatic detection and highlighting of deadlock conditions (see Figure 1 below). Now when you open an Oracle trace file that contains deadlock conditions, Toad will automatically:
Note – Here is a sample trace file (zipped) containing a deadlock so you can test drive this new feature.
Figure 1: Trace File Browser Deadlock Detection
From DBA perspective, Toad Trace file browser is one of the most used features in mine work.
It shows pretty good initial look and give me opportunity to solve 80-90% of all problems.
For finest tuning trca is swiss tool...which is totally different kind of tool with known problems on bigger trace files (few GB) which Toad can analyze without problems.