Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Import extent size problems

Re: Import extent size problems

From: <fitzjarrell_at_cox.net>
Date: Thu, 23 Aug 2007 09:08:49 -0700
Message-ID: <1187885329.608654.109490@x40g2000prg.googlegroups.com>


On Aug 23, 10:40 am, stephen O'D <stephen.odonn..._at_gmail.com> wrote:
> > Reading the documentation is always worthwhile:
>
> >http://download.oracle.com/docs/cd/B19306_01/server.102/b14215/exp_im...
>
> > Notice that compress defaults to y, and you're painfully aware of the
> > consequences. You need to set this parameter to n on the command line
> > or in your parfile:
>
> > exp .../... file=.... compress=n .....
>
> > This will prevent exp from 'resizing' the initial extent.
>
> I know what compress = y/n does - but if my original create table
> statement on the big database said
>
> "create table x .... storage initial 80M .... "
>
> Then will export not generate the DDL to have the same initial extent
> size if compress is N?

You might want to run:

set long 50000
select dbms_metadata.get_ddl('TABLE','<table name here>') from dual;

to see what Oracle believes the storage parameters to be. You might be surprised at what you find.

David Fitzjarrell Received on Thu Aug 23 2007 - 11:08:49 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US