onstat -d shows the amount of space allocated to tablespaces, not the amountactually used. So, if a table has 10GBytes allocated to it, and you delete
all the rows from it, the tablespace will still have 10GBytes allocated and
onstat -d will show no difference.
In order to influence the onstat -d figures you need to drop/re-add, or in
some other way, alter the table.
↪ replying to Neil Truby
In article <94efkt$ldu$1@taliesin2.netcom.net.uk>, Neil Truby
<ntruby@netcomuk.co.uk> writes
>onstat -d shows the amount of space allocated to tablespaces, not the amount>actually used. So, if a table has 10GBytes allocated to it, and you delete
>all the rows from it, the tablespace will still have 10GBytes allocated and
>onstat -d will show no difference.>
>In order to influence the onstat -d figures you need to drop/re-add, or in
>some other way, alter the table.
In both IDS & SE, rows deleted from a table do *not* reappear in the
free space unless the table is dropped and recreated. However the space
they *did* use is marked as available and is *reused* when more data is
loaded.
>
>
--
Surfer! My return is address at Hotmail.
If you really want to send me email then use:
surfer at
nevis-view dot
demon dot co dot uk
"I can resist anything but temptation" - Oscar Wilde ;-)