Digger is an Oracle extended trace analyzer. The key features of Digger that set it apart from any other Oracle extended trace analysis application are its intuitive user interface, high performance and advanced extended trace analysis capabilities.
Top 10 features
Graphical user interface
Unlike many of the Oracle trace analyzing tools, inlcuding tkprof, Digger is a GUI-based, not a command line tool. It means you don't have to learn all the options and command line switches. The analysis results are displayed in a pie-chart or a table and sorting by a value such as elapsed time is just a single mouse click away.
Sort by selected statistics, total waits or selected waits, include or exclude recursive SQLs, go to and analyze any SQL whether it's a top-level SQL or a recursive one. Pick any statement in the tree showing the structure and order of execution in the trace file and you can see its top contributors, full SQL text, bind variable values, actual execution plan along with various statistics such as affected rows or elapsed time.
Run once, analyze everything
Unlike tkprof or any other tool, once Digger swallows your trace file (and it does it pretty fast!) it knows all about it. No need to re-run it to sort by different criteria. You can slice and dice it to your heart's content. You can view it top-down or bottom-up, dig to any SQL, or a group of SQLs.
For every SQL statement in your trace file Digger shows you a graphical, intuitive, sortable execution plan with the actual statistics values found in the trace file. And since it is sortable you can click on any column to find out for example which execution step processed caused most consistent gets. Remember, these are actual values, not optimizer estimates!
Digger is very fast. In fact it loads most trace files withing seconds. To load a multi-gigabyte trace file takes only a couple of minutes. But most important is that it does it only once. Once the file is loaded you can analyze whatever aspect of your session performance is of interest to you. On a huge trace file this feature alone can save you hours of tedious work.
If you are curious enough to wonder what exactly was going on when your session was processing a SQL the Records view is for you. It shows the actual steps involved in the execution of a statement, like parse, bind, execute, fetch and waits, along with their description and vital statistics
Digger shows you the values of the bind variables for the SQL statements found in your trace file.
What was this wait event exactly... Never mind. You don't need to search. Digger shows you the detailed descriptions of wait events, database objects and abbreviations found in the trace file.
Load and compare multiple files
You can open more than one file at a time. Re-run your test session and load another file into Digger. You can easily switch between files by clicking on the open file tab if you need to compare the performance of the session before and after.
Easy to use
The user interface design of Digger is familiar and intuitive. You are unlikely to ever need to consult its manual to find out how to do something. The learning time is zero. Start Digger, load the file. Look at the pie chart to see what SQL contributed most to the statistics you are interested in. Click on this SQL pie slice to find out more. Digging is easy