Re: Next extent with Locally managed tablespace on 9i

From: Christian M. <cm_at_sdv.fr>
Date: Fri, 2 Aug 2002 11:57:37 +0200
Message-ID: <3d4a573d$0$211$4d4eb98e@read.news.fr.uu.net>

I've have create a LMT named "ENTETE" with uniform size=64KB I've imported my table.
After select * from dba_segments

    SEGMENT_NAME                  PROG
    SEGMANT_TYPE                   TABLE
    BLOCK                                    16384
    EXTENTS                                64
    INITIAL_EXTENT                   66355200
    NEXT EXTENT                        NULL

I've inserted rows until i have a new extent ! select * from dba_tablespace

TABLESPACE_NAM                 ENTETE
BLOCK_SIZE                             4096
INITIAL_EXTENT                     65536
NEXT_EXTENT                         NULL
MIN_EXTENTS                         1
MAX EXTENTS                         2147483645
PCTINCREASE                         NULL
MIN_EXTLEN                           65536
EXTENT_MANAGEMENT       LOCAL
ALLOCATION_TYPE               SYSTEM

SEGMENT_SPACE_MANAGEMENT MANUAL select * from dba_tables

SEGMENT_NAME                  PROG
SEGMANT_TYPE                   TABLE
BLOCK                                    18432
EXTENTS                                65
INITIAL_EXTENT                   66355200
NEXT EXTENT                        NULL

Why my next extent is 8M ( 2048) block ? Have know the value of the next extent if this value is NULL in DBA_TABLES ?

thanks

"Norman Dunbar" <Norman.Dunbar_at_lfs.co.uk> a écrit dans le message news: E2F6A70FE45242488C865C3BC1245DA70273F183_at_lnewton.leeds.lfs.co.uk...
> 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.
>
> 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.
>
>
>
Received on Fri Aug 02 2002 - 04:57:37 CDT