You were brought to this page based on an internet search
and as a free service to Oracle DBAs.
The text below is an except from the book,
Oracle Performance Firefighting, written by
Craig Shallahamer of
OraPub, Inc.
Figures and tables are not included on this page, only their reference.
To order the book in either print or PDF form, click
here.
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
PleaseOut of respect for those involved in the creation of the book and also for
their familes, we ask you to respect the copyright both in intent and deed. Thank you.
-------------------------------
The $ORACLE_HOME/bin/trcsess program consolidates trace files. You can even specify identification criteria, although when using DBMS_MONITOR, you probably have already effectively done this. The result is a single trace file ready to be formatted by tkprof, or whatever trace file parser/formatter you choose to use.
The $ORACLE_HOME/bin/tkprof program has been around as long as I can remember. Oracle continues to improve tkprof by adding wait event and timing information. Essentially, tkprof parses a trace file and formats for human readability. Other tools available that may better suit your budget, formatting, and analysis preferences.
At this point, you may have prepared a trace file for analysis, as well as possibly performance statistics. Now it's your turn to take this information and perform a session-level response-time analysis.
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
PleaseOut of respect for those involved in the creation of the book and also for
their familes, we ask you to respect the copyright both in intent and deed. Thank you.
|