Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Why tablespaces still need coalescing

Re: Why tablespaces still need coalescing

From: Wilko <Wilko_at_yoa.com>
Date: 2000/03/08
Message-ID: <8a6npq$or416@inetbws1.citec.com.au>#1/1

In article <952500528.7913.1.nnrp-14.9e984b29_at_news.demon.co.uk>, "Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote:
>
>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 ?
>
>

I understand that if all extent sizes are the same then coalescing is not necessary, however when I go into the svrmgr motive (graphic mode) the section on tablespaces is always telling me that the percent extents coalesed is less than zero, even though all my extent sizes are the same. How is this possible?

P.S. the minimum extent option is not available in 7.3

Thanks
Wilko Received on Wed Mar 08 2000 - 00:00:00 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US