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.
-------------------------------
* 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.
Residing in every Oracle data block's variable data area are structures called interested transaction lists (ITLs). These structures are largely responsible for Oracle's row-level lock and read consistency capabilities. From a highly abstracted perspective, you can think of ITLs like check boxes, as illustrated in Figure 6-35. Each check box is related to a specific transaction. If you want to update a row, but that locked row is already associated with another transaction's ITL, you will receive a TX enqueue wait-truly, a row-level lock.
©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.
|