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.
-------------------------------
To see a wonderful example of this, Figure 6-39 shows the inactive transactions flag change as a direct result of issuing a simple a select statement that touches block 1,78547.
Figure 6-39. Shown is a data block (1,75847) dumped immediately after a simple select statement touched the block. Notice the transaction flags have changed from a --U- to a C---, indicating a block cleanout has occurred.
Now I realize this is interesting and all that, but I also understand some readers may think this block dump and ITL stuff is not all that relevant. But I beg to differ. Not only have you gained a fuller understanding of the TX enqueue, but you have also clearly seen how Oracle implements its patented row-level locking scheme, In the next section, you will see how ITLs are involved with the "snapshot too old" error and with buffer cloning!
©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.
|