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.
-------------------------------
Figure 6-10. The OSM ipcbc.sql report shows the CBC-related instance parameters. This script output was the source of the data in Table 6-1.
If set, the number of buffers you want in the buffer cache (Oracle reserves the right to alter the actual number of buffers)
One of the best and easiest ways to cause CBC latch contention is to create a large buffer cache so your most active blocks are always cached, and then reduce the number of CBC latches to say, one. That should do it, except that Oracle is smart enough (at least starting with Oracle Database 10g) to not allow the number of CBC latches to drop below 1,024. But even with 1,024 latches and enough logical IO activity, you'll see plenty of CBC latch contention.
©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.
|