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 developers have some amount of control over the use of interim segments, many applications, along with their massive redo generation requirements, are simply transitioned over to the DBAs, who are told to somehow just make them perform. Global temporary tables give the DBA a near-application-level tool, which can be used to possibly avoid significant and painful application changes.
Global temporary tables share many standard data segment and temporary segment characteristics, such as the following:
* They can be created by a session using a create table variant. For example, instead of create table customers, the syntax could be create global temporary table customers.
©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.
|