RE: Reducing table initial extent size for subset of production

This will always happen if you usually import from the prod database to the test database.
The best possibility is to create table creatio scripts and index creation scripts and once the scripts are done you can edit the initial and next extents to what ever way you want,create these first and then use the import facility to import the other structures into the database this is how I am doing and able to save space on my test database. But there might be another ways this just my opinion check out others.

>From: Steven Monaghan <Steve.Monaghan_at_wcom.com>
>Reply-To: ORACLE-L_at_fatcity.com
>To: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com>
>Subject: RE: Reducing table initial extent size for subset of production
>Date: Mon, 19 Jun 2000 04:06:28 -0800
>
>TOAD has a function to build a table/index/synonym creation script. Again,
>you would have to manually resize the tables, but it would be a good start.
>I think the free version is still available at www.toadsoft.com
>
>Steve Monaghan
>
> > -----Original Message-----
> > From: root_at_fatcity.com [mailto:root_at_fatcity.com]On Behalf Of Linda
> > Hagedorn
> > Sent: Friday, June 16, 2000 2:31 PM
> > To: Multiple recipients of list ORACLE-L
> > Subject: Reducing table initial extent size for subset of production
> >
> >
> > I inherited an export/import process to create a subset of production
>data
> > for development and QA use. It's consistently running out of space.
> >
> > The goal is to create a duplicate production database on a test
>platform,
> > delete rows and/or truncate specific tables, export the tables
> > and data, and
> > import the reduced-volume tables.
> >
> > In reviewing the MetaLink doc 61949.1 Export and Import Bulletin, it's
> > saying COMPRESS will alter the initial size to be the currently
>allocated
> > size, despite the contents or lack thereof. This explains why I'm
>running
> > out of space, even after deleting a significant portion of the data.
> >
> > To reach my goal of smaller tables, do I have to 1) export without
> > compression, 2) preallocate all 200+ tables, and 3) import, or is there
> > another way? If I have to preallocate the tables, does someone
> > have SQL to
> > generate the DDL statements, including the size math to recalucluate the
> > tables smaller?
> >
> > Any input is appreciated. Thanks.
> >
> > Linda Hagedorn
> >
> > --
> > Author: Linda Hagedorn
> > INET: Linda_at_pets.com
> >
> > Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
> > San Diego, California -- Public Internet access / Mailing Lists
> > --------------------------------------------------------------------
> > 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).
> >
>
>--
>Author: Steven Monaghan
> INET: Steve.Monaghan_at_wcom.com
>
>Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
>San Diego, California -- Public Internet access / Mailing Lists
>--------------------------------------------------------------------
>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).