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.
-------------------------------
Oracle9i Release 2 and later have multiple redo allocation latches available, and the redo copy latches are normally not required. In summary, the redo log buffer works like this: A server process contends for one of the redo allocation latches, acquires one, allocates redo log buffer space, copies its redo into the redo log buffer, and releases its redo allocation latch. In more detail, it works like this:
* The server process gets the memory address of the last allocation pointer, which is marker MK100 in Figure 8-3.
* The server process adds the redo bytes it needs to marker MK100 and moves the pointer clockwise, perhaps to marker MK200.
©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.
|