Re: really? Empty Datafile/Tablespace? and RESIZE ???

The reason you cannot shrink the tablespace after truncating the tables is that the tablespaces high-water mark is still 'up there'.

Failing that, it could be down to the way you create your tables. If you make a 100mb table, then create a 200mb table and truncate them both, you will still have an empty table starting 100mb into the file...

wolf_at_wondersoft.de (Ric) wrote in message news:<abb2933c.0112120746.567cccd2_at_posting.google.com>...
> Hi.
> Someone of our developers wants to Resize automatically the Datafiles
> which are assigned to his application .
> Not that i like his idea, but I need your help to proof that he perhaps
> does things you should not do.
> There are n tables where some contain LOBS.
> Then ALL tables are "truncated".
> The datafile should then be empty.
> But the ALTER TABLE ... RESIZE gets the "data beyond" error.
> There should not be any more data.
> Is that because Oracle has some internal things stored?
> Is that because LOBS go different? Is the space for them not
> really freed? Are there some internals?
> Don't misunderstand me, I want to have hints to be able to
> proof that the resize is not good (not only because of later performance
> reasons etc.) or sometimes not possible.
> This guy complained this must be a bug of Oracle, I think it is not,
> because Oracle must have the freedom of organizing it's space by itself.
>
> Thank you in advance ,
> please excuse my bugs in writing, i am no native english person.
> Ric
Received on Fri Dec 14 2001 - 15:41:25 CET