Re: Problem with import of a ~2Gig table

Hans, can you confirm this ? I thought they are two differnt option(s) and are not related.
Ted chyn

In article <7pbvbb$kb4_at_romeo.logica.co.uk>,   "Hans den Broeder" <broederh_at_logica.com> wrote:
> when you make an export using direct=y, then setting a buffersize for
the
> import doesn't make any sense since import - in this case - doesn't
use the
> buffer cache.
>
> Mario Bucsics wrote in message
> <2750ac20.ad7eeca6_at_usw-ex0107-050.remarq.com>...
> >Hi
> >
> >
> >You can export the table from the first database with this
> >command very fast:
> >
> >exp user/pass file=file.dmp full=y log=file.log direct=y
> >
> >
> >If you like to import the Table fast you should make a
> >rollback segment with the same size as the export file + 10
> >% more. Set all other rollback segments offline an start the
> >import with the following command:
> >
> >imp user/pass file=file.dmp full=y log=file.log
> >
> >When you are rar in space then you could add the parameter
> >"commit=y" to the import. This needs much longer as the
> >import with the big rollback segment.
> >
> >If you change the directory to "$ORACLE_HOME/rdbms/lib" and
> >type "make impst" a single server import is generated. You
> >can use the impst instead of imp to import data faster too.
> >
> >
> > Regards
> >
> > Mario Bucsics
> >
> >* Sent from RemarQ http://www.remarq.com The Internet's Discussion
Network
> *
> >The fastest and easiest way to search and participate in Usenet -
Free!
> >
>
>

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't. Received on Thu Aug 19 1999 - 13:14:47 CDT