RE: Extent allocation for objects

It's a characteristic of uniform size. If you have uniform size 512 M, then you can't have an extent that is any other size. So you can specify initial extent and next extent until you're blue in the face, but you will always get 512 M extent sizes. See? Maybe LMT is quite the grand panacea.

> -----Original Message-----
>
> Let me give you the scenarios. Maybe I can get a good
> explanation from
> someone.
>
> Tablespace A locally managed uniform extents size 512M.
> Tablespace B locally managed uniforma extents size 1M.
>
> 1) Create table TabA tablespace A. Insert data, and it has 1
> extent of
> 512M even though the table size is only 76M. This makes sense.
> 2) Create table TabA tablespace B. Insert data, and it has
> 76 extents of
> 1M each. This makes sense.
> 3) Create table TabA tablespace A. Same as scenario 1. Alter
> table TabA
> move tablespace B. Creates 512 extents of 1M each. Why?
> The table only needs 76M of space. Why create all those
> additional
> extents?
>

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Stephen Lee
  INET: Stephen.Lee_at_DTAG.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).