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>Some redo-related performance issues can be solved with instance parameters and fancy Oracle features. However, the large majority of difficult redo issues are the direct result of the application generating far more redo than the IO subsystem can quickly service. This puts pressure on changing the application code, which many times is deep within the application's procedural code. This entices the performance analyst to sometimes get very creative and consider options like in-memory file systems or using the commit write facility described earlier in the chapter. But whatever the issues may be, remember to consider and evaluate solutions focused on Oracle, the operating system, and the application.
p><p>The remainder of this chapter addresses the key redo-related wait events shown in Table 8-2. I will describe the problem and then provide a number of tactics and solutions to resolve it.
p><p>The process is waiting for its commit to complete or its trigger to the log writer to write to complete.
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!
|
