Locally managed tablespace / truncate BUG ?

Giganews Newsgroups
Subject: Locally managed tablespace / truncate BUG ?
Posted by:  G Dahler (yellow-shark@spamex.com)
Date: Tue, 13 Apr 2004

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 ?

Replies