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.
-------------------------------
Figure 5-1. Since this instance has started, it has consumed 734 seconds of CPU. Statistic 12 from the classic instance statistics view v$sysstat contains the CPU time, in hundredths of a second, since the instance has started.
As I stressed in previous chapters, most of our diagnostic work is based on an interval of time. To capture interval activity, we need both an initial value and a final value. Figure 5-2 shows a simple example of how to capture instance CPU consumption over a 30-second interval. This strategy can be applied to any similarly structured Oracle table or view, including the performance views.
Figure 5-2. Most firefighting requires interval reporting. This figure shows an example of how simple it can be to capture and report interval data from v$sysstat or any similarly structured performance view.
©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.
|