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.
-------------------------------
Now with the latch in hand, you begin traversing CBC 02 in the hope of finding buffer 35,2435. You check buffer header BH 165 and discover it is associated with another buffer, so you move onto buffer header BH 145. You discover this buffer header is associated with another buffer, so you continue. But you hit the end of CBC 02, and therefore you know that buffer 32,2435 is not in the buffer cache. You release the CBC latch CS 800.
You still need to access the buffer, so you can't simply give up. While the buffer is not in memory, it is in a database file on disk (otherwise the data dictionary would not have showed this block was of interest to you). So you must make a system call to the IO subsystem requesting your single block. Just before you make the IO request, you ask the operating system for the time by issuing the gettimeofday system call. While you are waiting for the operating system to return the block, you are yelling, "db file sequential read!"
When you finally get the block from disk, you again issue a gettimeofday call, calculate the time difference, and record that into Oracle's wait interface structures for anyone to see via wait event views. Now with the block in hand, you still cannot peek inside, as it must first be appropriately placed in the buffer cache and all the relevant memory structures must be appropriately changed. How this is performed is what much of the rest of this chapter is about.
©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.
|