Re: Import ora-1658 initial extent size

How about precreating empty tables and then doing the import with ignore=y?

FWIW I think that the default of Y for the COMPRESS parameter to exp is just about the most annoying thing in the utility.

--
Niall Litchfield
Oracle DBA
Audit Commission UK
"Howard J. Rogers" <howardjr_at_www.com> wrote in message
news:3a9e4980$1_at_news.iprimus.com.au...


>

> "Nuno Souto" <nsouto_at_nsw.bigpond.net.au.nospam> wrote in message

> news:3a9e1ee7.4806234_at_news-server...

> > On Thu, 1 Mar 2001 11:06:59 +0100, "Peter Laursen" <ptl_at_edbgruppen.dk>

> > wrote:

> >

> > >

> > >"Nuno Souto" <nsouto_at_nsw.bigpond.net.au.nospam> skrev i en meddelelse

> > >news:3a9e14bf.2206409_at_news-server...

> > >>

> > >> destroy=n  ?

> > >>

> > >Sorry, you misunderstand me. I have allready created tablespaces and

> > >datafiles and these must be used. The problem is in the size of the

 initial


> > >extent given in the exportfile.

> >

> > Then ignore=y should work.  It bypasses that sort of error and keeps

> > going, if tables/indexes are already defined.  Or am I still not

> > seeing the problem?

>

>

> I rather thought the problem was that he created the export file with

> compress=y, and hence the import is trying to create mammoth initial

> extents... and his files simply aren't big enough to accomodate the

 required


> amount of contiguous tablespace.

>

> The only thing I can think of if that's the case is to make the

 tablespaces


> autoextensible, or doing a manual resize upwards.  Adding extra datafiles

> won't work, because extents must be contained within the one physical

 file.


>

> Regards

> HJR

>

>

>

>

>

>

>

> >

> > Cheers

> > Nuno Souto

> > nsouto_at_bigpond.net.au.nospam

> > http://www.users.bigpond.net.au/the_Den/index.html

>

>