exp/imp copy initial extent

From: Norman Dunbar <Norman.Dunbar_at_lfs.co.uk>
Date: Tue, 1 Oct 2002 08:32:13 +0100
Message-ID: <E2F6A70FE45242488C865C3BC1245DA702B9BD87@lnewton.leeds.lfs.co.uk>

Or, in case they want to do it again, contact me if you have C++ compiler on your system (Unix ?) and I'll send you the source code for a 'filter' which removes storage parameters INITIAL, NEXT, PCTINCREASE, MINEXTENTS and MAXEXTENTS. It can also remove the username and tablespacename if you wish.

I use it at times when I get a customer dump from my favourite customer who insists that one extents worth of data improves performance no end and exports/imports every night to get everything in one extent. (He also thinks that running an OLTP system using PARALLEL iimprtoves responses too ! )

Cheers,
Norman.

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: susana73_at_hotmail.com (Susan Lam) [mailto:susana73_at_hotmail.com] Posted At: Tuesday, October 01, 2002 2:19 AM Posted To: server
Conversation: exp/imp copy initial extent Subject: exp/imp copy initial extent

I got a dmp file from a business partner and I need to import it to our database. The dmp file is only 1M but after I import it occupies 1GB! The reason is they set the initial extent of all tables, index to 20M even they don't have much data at all. I tried make the tablespace locally manage with "autoallocate" or "uniform size" before importing but it does not help.

Is there any way to fix the initial extent size? The only way I know is edit/modify all the tables/indexes script to change the extent size before importing but I do not want to do it.

Thanks,
Susan Received on Tue Oct 01 2002 - 02:32:13 CDT