RE: dropping Undo Tablespace

From: <oracle-l-bounce_at_freelists.org>
Date: Thu, 31 May 2007 16:05:49 -0400
Message-ID: <E2157B37A63D2E4B9B00575021FC84D6014B2308@tshusmian2msg01.ERF.THOMSON.COM>

With judicious use of transaction suspension and resumable timeout periods, one can generally avoid such incidents. Even without this capability, given the choice of having a transaction fail because of an out-of-space condition (a) in a tablespace consisting of non-AUTOEXTEND datafile(s), or (b) in the filesystem in which such files live, I'd choose the former every time, since in general it's easier to recover from the first than the second.

---

Jim Silverman
Senior Systems Database Administrator
Solucient, LLC - A Thomson Company
Telephone: 734-669-7641

FAX:            734-930-7611
E-Mail:         jim.silverman_at_thomson.com

-----Original Message-----

From: Ted Coyle [mailto:oracle-l_at_webthere.com] Sent: Thursday, May 31, 2007 3:55 PM
To: Silverman, James (TH USA); godwin.ror_at_gmail.com; oracle-l_at_freelists.org
Subject: RE: dropping Undo Tablespace

So you'd rather have a business transaction/batch process fail?

Unfortunately, I can't answer your question. However, the situation you describe perfectly illustrates my loathing for using AUTOEXTEND ...

Ted

No virus found in this outgoing message. Checked by AVG Free Edition.
Version: 7.5.472 / Virus Database: 269.8.4/825 - Release Date: 5/30/2007 3:03 PM  

--

http://www.freelists.org/webpage/oracle-l Received on Thu May 31 2007 - 15:05:49 CDT