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.
-------------------------------
* Increase the buffer cache. If there is memory available, increase the buffer cache. This will allow more room for buffers, which increases the likelihood of finding a free buffer.
* Increase database writer pull power. For example, increase the number of database writers. Do anything you can think of to help the database writers increase their rate of dirty buffer writing. Unless the buffer cache is grossly undersized, this is probably your best Oracle-focused solution.
* Increase _db_writer_max_scan_pct. This will give the database writer more time to flush its write list. This could result in LRU chain latch contention, because the server process searching for free buffers will be searching more buffers before giving up and posting a free buffer waits event.
©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.
|