Re: Locally managed tablespace / truncate BUG ?

G Dahler wrote:
>
> 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 ?

The TRUNCATE command will not release storage below its initial allocation. With LMTs, this does not mean release down to one extent. It means release down to its intiail allocation of extents, in your case, 22 extents was initially allocated.

HTH,
Brian

-- 
===================================================================

Brian Peasland
dba_at_remove_spam.peasland.com

Remove the "remove_spam." from the email address to email me.


"I can give it to you cheap, quick, and good. Now pick two out of
 the three"