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.
-------------------------------
Look at the rtsysx.sql command line in Figure 2-15. The second parameter is 10. If you use 100 as the parameter, then all SQL statements captured during the report interval that have the same first 100 characters are counted and displayed. And only statements with a count greater than 1 are shown.
Figure 2-17 shows that only two SQL statements had the same first ten characters, and each of these occurs only twice. So it appears that nonbind variable SQL is not an issue. When nonbind variable SQL is an issue, this section may show hundreds of SQL statements with the first 100 characters exactly the same. An equivalent OSM script is simsql1.sql.
Figure 2-17 shows the last section of rtsysx.sql, displaying the operating system CPU utilization details. Starting in Oracle Database 10g, Oracle captures operating system CPU details and makes the information available through the v$osstat view. Chapter 5 provides more details about the v$osstat view, and Chapter 4 discusses the CPU utilization components.
©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.
|