Re: Export Tablespaces

FlameDance wrote:

> Niall Litchfield wrote:
>
>  > The point is that if all
>
> > datafiles are 2gb and the table is larger than 2gb the create table
> > statement in the import *will* fail. 
>
>
> That'll be my next worry. Regardless of compress=y or compress=n? Or 
> does you proposal of compress=n solve the issue?
>
>  > Actually if the table is 1.7gb and
>
> > isn't in a tablespace on its own and isn't the first object imported the
> > import is already likely to fail for lack of 1.7gb contiguous space to
> > create the initial extent.
>
>
> I can enforce that by importing only that table in a first import run. 
> Problem is, on the next import run with all objects I get millions of 
> unique key violations on that table, even with ignore=y set.
>
> Can I exclude a certain object from an import run?
> If yes, how?
> If not, can I suppress the unique key violation messages?
>
> Stephan
The compress option of the exp program has *nothing* to
do with the size of the output file.
It will recalculate your initial and next settings in the
create table statement, unless the table was created with
the nocompress option (did that exist in 8i?)


--
Regards, Frank van Bortel