Re: Locally managed tablespace / truncate BUG ?

From: G Dahler <yellow-shark_at_spamex.com>
Date: Tue, 13 Apr 2004 14:22:09 -0400
Message-ID: <idWec.6392$2Z6.557425@news20.bellglobal.com>

"G Dahler" <yellow-shark_at_spamex.com> a écrit dans le message de news:P5Wec.6384$2Z6.556128_at_news20.bellglobal.com...
> I've imported a table into a locally managed tablespace with automatic
> allocation of extents. It created 22 extents of 1 mb each. The table was
> exported with compress=N from a dictionnary managed tablespace;
>
> I have truncated the table with the "drop storage" clause.
>
> According to the user_extents view, I still have 22 extents and the table
> still uses 22 mb of storage.
>
> What's wrong ?
>

It wasn't a bug. The darn table already had been reimported in the prior dictionnary tablespace with a "compress=y" option and had it initial extent set to 22 Mb.

Now I needed to import this table empty and I end up with the allocation of 22 useless extents (and a waste of space)

I will have to MOVE the table in the same tablespace, changing the initial extent to fix it. Received on Tue Apr 13 2004 - 13:22:09 CDT