Return-Path: Received: from ensim.rackshack.net (root@localhost) by orafaq.net (8.11.6/8.11.6) with ESMTP id gBD1g8D22326 for ; Thu, 12 Dec 2002 19:42:08 -0600 X-ClientAddr: 209.68.248.164 Received: from newsfeed.cts.com (newsfeed.cts.com [209.68.248.164]) by ensim.rackshack.net (8.11.6/8.11.6) with ESMTP id gBD1g7322321 for ; Thu, 12 Dec 2002 19:42:07 -0600 Received: from fatcity.UUCP (uucp@localhost) by newsfeed.cts.com (8.9.3/8.9.3) with UUCP id OAA60385; Thu, 12 Dec 2002 14:24:56 -0800 (PST) Received: by fatcity.com (26-Feb-2001/v1.0g-b72/bab) via UUCP id 00518EBE; Thu, 12 Dec 2002 13:53:46 -0800 Message-ID: Date: Thu, 12 Dec 2002 13:53:46 -0800 To: Multiple recipients of list ORACLE-L X-Comment: Oracle RDBMS Community Forum X-Sender: Paula_Stankus@doh.state.fl.us Sender: root@fatcity.com Reply-To: ORACLE-L@fatcity.com Errors-To: ML-ERRORS@fatcity.com From: Paula_Stankus@doh.state.fl.us Subject: RE: UNDO RETENTION Organization: Fat City Network Services, San Diego, California X-ListServer: v1.0g, build 72; ListGuru (c) 1996-2001 Bruce A. Bergman Precedence: bulk Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2A228.D20F12F0" ------_=_NextPart_001_01C2A228.D20F12F0 Content-Type: text/plain; charset="iso-8859-1" Having had frustration with rollback segments from time to time over the years I am happy to let Oracle handle it with their recommended automatic undo management and a defined undo tablespace. However, it isn't that simple is it? I imagine that undo retention is critical and if you specify too long you might have problems with performance while too little and what you loose read-consistency - any ideas on the best way to configure this little bugger? ------_=_NextPart_001_01C2A228.D20F12F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: UNDO RETENTION

Having had frustration with rollback segments from = time to time over the years I am happy to let Oracle handle it with = their recommended automatic undo management and a defined undo = tablespace.  However, it isn't that simple is it?  I imagine = that undo retention is critical and if you specify too long you might = have problems with performance while too little and what you loose = read-consistency - any ideas on the best way to configure this little = bugger? 

------_=_NextPart_001_01C2A228.D20F12F0-- -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: INET: Paula_Stankus@doh.state.fl.us Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru@fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).