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.
-------------------------------
While the TX enqueue is known as the row-level lock enqueue, there are actually three reasons for a TX enqueue to be posted, and only one of those is actually a row-level lock. Figure 6-34 is very similar to Figure 6-1 shown at the beginning of this chapter. Every Oracle data block can be abstracted into three areas:
* The row data contains the actual Oracle rows and is just one of the important parts of every data block.
Figure 6-34. An Oracle data block model containing the three main block parts. Notice the block's free space can be decreased by growth from both the variable and row data areas.
©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.
|