Craig Shallahamer's Blog
|
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.
Please—Out 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.
-------------------------------
<p>* Tune logical IO SQL. The CBC structure becomes stressed when the answer to the question, "Is the buffer in the buffer cache?" is nearly always "Yes!" If the answer shifts to "No, it's not in the cache," you will notice sequential or scattered reads will be the issue. So, from an application perspective, look for the SQL that performs the majority of buffer gets, that is, logical IO activity. The SQL statement or statements will be there-they must exist. Do whatever you can to reduce their logical IO consumption. This means classic SQL tuning, including indexing, as well as reducing the execution rate during the performance-critical times.
p><p>* Increase CPU power. In most cases, the CPU subsystem will be heavily utilized and probably the operating system bottleneck. Latch acquisition and the associated memory management consume a tremendous about of CPU. Do anything you can think of to reduce CPU consumption and to increase CPU capacity. Look for processes that do not or should not be running during peak times. Consider adding CPUs or using faster CPUs. If you are running in a virtual environment, considering ensuring this Oracle system has increased CPU resources. However, be aware that unless the application workload has considerably increased, additional CPU power typically will be consumed rather quickly. The real solution probably lies elsewhere. Increasing CPU power may be a good quick fix, but it will probably not truly solve the problem.
p><p>* Check for cloning issues. Whenever I encounter CBC latch contention, I check to ensure cloning is not the issue. This is rarely the case, but if it is, the solution path (as outlined previously) is very different from all the other solutions.
p>
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
Please—Out 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.
|
|
Know what's important before it's too late!
OraPub's
Performance Training
is like no other...
More Class Pics...
Get student testimonials!
|
