Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Why tablespaces still need coalescing
The tablespace does not need coalescing.
This is NOT because some magic makes
it happen invisibly and automatically, its
just because it isn't necessary.
If all extents are the same size, all the
holes left by dropping an object are the
same size (although adjacent ones will
coalesce as the drop take places, so
some holes will be multiples of the
'unit hole-size'.
Since all the holes are 'the correct size'
the next time you create an object, it
will pick some of the available holes
straight away without having to thrash
around looking for a large enough chunk
and without leaving odd little bubbles of
space all over the place.
N.B. Have you also set MINIMUM EXTENT
for the tablespace as well is initial, next
and pctincrease ?
-- Jonathan Lewis Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk Wilko wrote in message <8a4c7n$or49_at_inetbws1.citec.com.au>...Received on Wed Mar 08 2000 - 00:00:00 CST
>
>I am using oracle 7.3 and all the extents are the same size
>each tablespace. However, the tablespaces still need coalescing.
>
>Any ideas?
>
![]() |
![]() |