I'm pretty sure that the "non-coalesced contiguous free space extents"
situation does not apply to a locally managed tablespace. At least
that's what the manual says and I haven't looked further than that.
> -----Original Message-----
> From: Rachel Carmichael [mailto:wisernet100_at_yahoo.com]
>
> But Oracle would coalesce on the fly, as necessary.
>
> I forget the order of the first two (it's been awhile!) but as I
> recall, Oracle would look for:
>
> 1) an extent of exactly the same size as required
> 2) an extent larger than that required
> 3) "contiguous" extents that had not yet been coalesced which made up
> the correct size (or larger)
>
> Rachel
> --- Richard Foote <richard.foote_at_bigpond.com> wrote:
> >
> > But until the "contiguous" extents get coalesced, they would be not
> > be
> > treated as contiguous by Oracle.
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Jacques Kilchoer
INET: Jacques.Kilchoer_at_quest.com
Fat City Network Services -- 858-538-5051 http://www.fatcity.com
San Diego, California -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
Received on Wed Apr 16 2003 - 16:30:13 CDT
