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.
-------------------------------
Figure 3-7. Second part of the pseudocode for when a process ask for a latch. The three core supporting functions are depicted; fast_get, spin_get, and sleep.
Once the address of the child latch is known, the developer must also know whether the latch should be acquired in shared mode or exclusive mode. Shared mode is likely to be acquired more quickly, because multiple processes can share a latch, but only one process can acquire and hold a latch in exclusive mode. If the memory structure is only to be scanned, but not changed, then perhaps the developer can ask for the latch in shared mode. But if the memory structure is going to be altered in some way, an exclusive mode request is required.
The developer also needs to know if the latch request type is immediate or willing to wait. An immediate latch request, sometimes called a nowait request, is a single "give me the latch this instant" request. This is commonly called a fast get, and this Fast_Get function is shown in Figure 3-7.
©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.
|