Re: Import extent size problems

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?

It will, which is why I believe that compress is not set properly for your export.

David Fitzjarrell Received on Thu Aug 23 2007 - 11:00:26 CDT