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.
-------------------------------
Once the definition of requirements is set, the data must be collected. Most Oracle systems now collect Statspack or AWR data, which means the data collection is currently occurring for you. Your job is to extract the necessary information.
When gathering CPU requirements, we typically look at the time model system statistics (v$sys_time_model) or the instance statistics (v$sysstat). In previous chapters, I have presented how to gather CPU requirements from the v$sesstat, v$sysstat, v$ses_time_mode, and v$sys_time_model views.
The second part of Figure 9-2 shows a few instance statistics from a Statspack report. Based on this data, during the Statspack reporting interval, Oracle processes consumed-that is, required-1,675,794 centiseconds of CPU, which is 16,757.94 seconds of CPU.
©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.
|