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-4 shows the one-to-one relationship between a buffer header, its associated buffer, and its data block. As illustrated in Figure 6-4, the buffer headers contain, in part, where a buffer resides in the buffer cache, where the associated block resides on disk, and when the buffer was last read from disk. If you hear kernel developers talking about a DBA, they are not referring to you! They are referring to a block's disk address, which is called the data block address, or DBA for short.
Figure 6-4. There is a one-to-one relationship between a buffer header (BH 100), its cached buffer (CB 330), and its on-disk data block (DBA 5,320). List manipulation occurs at the buffer header level, buffer changes occur in the cached buffer, and block changes occur at the disk level.
Have you ever wondered why there is no view v$bc for the buffer cache? That's because a buffer and a block's metadata are stored in the buffer header, and it's the metadata we usually need for our performance analysis. So the view is named v$bh, for buffer header.
©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.
|