Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: truncate command 8.1.7. locally managed tablespaces

Re: truncate command 8.1.7. locally managed tablespaces

From: Frank <fvanbortel_at_netscape.net>
Date: Wed, 21 May 2003 22:01:56 +0200
Message-ID: <3ECBDB34.9090801@netscape.net>


Howard J. Rogers wrote:
<snip!>
>
> 50% PCTINCREASE has been the default value for Oracle since year dot.
> It's a disgraceful default, and should always be changed to zero,
> without exception.
>

The only exception being SYSTEM in pre-9i (and I'm just stating that because I do not know exactly how 9i would behave) instances. 9i with LMT SYSTEM would be OK, but DMT?

If your system TS (on pre-9i) reaches max_extents, you're likely to get stuck between a rock and a hard place. Saw that happening to a 7.x db once; it came to a grinding halt, and could not be brought back to life, restoring backups was the only option. Cannot think of a reason why that would have been improved in 8.0 or 8i.

Of course, it depends... on the table being hit, for one. But, better safe than sorry.

-- 
Regards, Frank van Bortel
Received on Wed May 21 2003 - 15:01:56 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US