Next extent with Locally managed tablespace on 9i

From: Norman Dunbar <Norman.Dunbar_at_lfs.co.uk>
Date: Fri, 2 Aug 2002 09:34:07 +0100
Message-ID: <E2F6A70FE45242488C865C3BC1245DA70273F183@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 - 03:34:07 CDT