Re: Importing tables w/large initial extents into a small database

From: Joel Garry <joelga_at_pebble.org>
Date: Fri, 08 May 1998 18:05:05 GMT
Message-ID: <slrn6l6ibd.aes.joelga@pebble.org>

On Wed, 06 May 1998 23:56:40 GMT,
Jonathan Gennick <gennick_at_worldnet.att.net> wrote:

>Today I needed to setup an empty copy of a database in order
>to do some testing. I took an export of the database using
>the following command:
>
> exp73 owner=XXX file=ffff log=llll ROWS=N
>
>Even though no data was exported, all the CREATE TABLE
>statements in the export file contained storage clauses with
>very large initial extents. So in order to load this export
>file into another database, I had to allocate a very large
>tablespace to hold a bunch of empty tables. Is there a way
>to do the import in such a way that the tables are recreated
>using the default storage parameters defined in the target
>database?

If you are brave and careful, you can edit the ffff.dmp to have whatever storage characteristics you want. You have to be careful because there are special characters that imp uses in there. I often just strip out the creation statements to another file and convert them to sql with some judicious global replacing in my favorite editor.

An alternative is to get one of the various collections of scripts that makes sql create statements from your dictionary. See the tools links off my homepage, or use dejanews to find stuff that's been posted (search for "jared still" for one recent one).

>
>

--
These opinions are my own and not necessarily those of Information Quest

jgarry@eiq.com                           http://www.informationquest.com

http://ourworld.compuserve.com/homepages/joel_garry "See your DBA?" I AM the @#%*& DBA! Received on Fri May 08 1998 - 13:05:05 CDT