Re: Import extent size problems

From: stephen O'D <stephen.odonnell_at_gmail.com>
Date: Thu, 23 Aug 2007 08:40:42 -0700
Message-ID: <1187883642.820547.286130@r23g2000prd.googlegroups.com>

> 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? Received on Thu Aug 23 2007 - 10:40:42 CDT