Re: Next extent with Locally managed tablespace on 9i

Hi Kenneth,

Maybe I wasn't being pedantic.

I resay what I mentioned earlier in this thread (as I foolishly used html which you or others may not be able to view properly). Basically the "way" INITIAL, NEXT, etc. are interpreted is different with LMT.

Just being a little pedantic I know but NEXT is not ignored when you create a segment in a locally managed tablespace. It's used along with INITIAL, PCTINCREASE and MINEXTENTS to calculated the initial size of the segment. This
initial size is then used to determined the extent size(s) with autoallocate or is divided by the uniform size to determined the initial number of extents. This is to ensure existing scripts designed to create segments of an initial size still have the same behavior regardless of the type of tablespace used (strange but true).

Once the segment has been created, NEXT and PCTINCREASE have no further effect. MAXEXTENTS is however
totally ignored (unfortunately).

I'm only guessing, but I wouldn't be surprised to see most if not all these go in 10i.

Cheers

Richard

Kenneth, Koenraadt wrote:
>
> On Fri, 2 Aug 2002 09:34:07 +0100 , Norman Dunbar
> <Norman.Dunbar_at_lfs.co.uk> wrote:
>
> >Christian,
> >
> >if you have an LMT set with uniform size = 64KB then when you import a
> >table with INITIAL = 64M then you will actually get 1024 extents of 64K
> >rather than one of 64M.
> >
> >The behaviour you mention is what happens with a DMT.
> >
> >Make sure you create your LMT with 'extent management local uniform size
> >...' for best results.
> >
> >
> >HTH
> >
> >Regards,
> >Norman.
>
> Hi Norman,
>
> A strange thing about this :
>
> I tried to import a table with zero rows and INITIAL= 4 M into a LMT
> with extent size 1M. Afterwards, DBA_SEGMENTS showed initial_extent =
> 4 M, but extents = 4 ! So the tablespace organises the table with 4 x
> 1M extents, but claims that it's intial extent is 4 M......
>
> - Kenneth Koenraadt
>
> >PS. To refrain EXP from creating an INITIAL extent equal to the size of
> >the table, make sure you exp with COMPRESS=N because this setting is the
> >default. Unfortunately, if the table in question has ever been
> >exported/dropped/imported then it will have been created with a large
> >INITIAL and NEXT and setting COMPRESS=N won't really make much of a
> >difference - unless there is more data in the table since it was last
> >imported.
> >
> >-------------------------------------
> >Norman Dunbar
> >Database/Unix administrator
> >Lynx Financial Systems Ltd.
> >mailto:Norman.Dunbar_at_LFS.co.uk
> >Tel: 0113 289 6265
> >Fax: 0113 289 3146
> >URL: http://www.Lynx-FS.com
> >-------------------------------------
> >
> >
> >-----Original Message-----
> >From: Christian M. [mailto:cm_at_sdv.fr]
> >Posted At: Friday, August 02, 2002 9:10 AM
> >Posted To: server
> >Conversation: Next extent with Locally managed tablespace on 9i
> >Subject: Next extent with Locally managed tablespace on 9i
> >
> >
> >Hi,
> >
> >I want to migrate on 9i.
> >Before I was using DMT but now the default tablespace is LMT.
> >Then, I have created my new database with LMT and I have Imported data.
> >
> >The problem is that IMP create my tables with an INITIAL parameter equal
> >as
> >the size of the table.
> >Or with LMT, INITIAL = NEXT !
> >
> >So if I have a table created by the import utility with an Initial
> >extent
> >of 64M, is the value of the next extent : 64 M ? If then, how can i
> >change
> >this value ?
> >
> >Thanks in advance.
> >
> >Christian.
> >
> >
> >