Re: truncate command 8.1.7. locally managed tablespaces

From: Paul Brewer <paul_at_paul.brewers.org.uk>
Date: Tue, 20 May 2003 20:23:12 +0100
Message-ID: <3eca80e7_1@mk-nntp-1.news.uk.worldonline.com>

"Bob" <where_was_you_at_btinternet.com> wrote in message news:733fcc55.0305191125.4d95064f_at_posting.google.com...
> The truncate command on non uniform locally managed tablespaces leaves
> the next extent and pct_increase intact instead of taking the default
> values from the tablespace as for dictionary managed. Next time
> records are inserted beyond the initial extent size then it uses the
> next extent size for its calcxulation worst it then multiplies it by
> 1.5 (50% pct_increase shrink wrapped oracle applications). This was
> noted in a migration program that truncated all old rows for a
> previous run before importing more and eventually reached a 12.9G next
> extent before space could not be allocated after about 23 such
> migrations.
> Does anyone know if this is a bug or a feature all the stuff I've read
> says it ignores both next extent and %increase.

Personally, I wouldn't even worry about it. I'd just go for uniform size LMT all the time.

Regards,
Paul Received on Tue May 20 2003 - 14:23:12 CDT