Re: Importing huge data

Yeah!!!!!!! I think we've got a convert!!!!!

Cheers,
Brian

Jay wrote:
>
> Thank you guys.
> I'm going with
> NOLOGGING and a Direct path load in SQL*Loader
>
> -Jay
>
> "Brian Peasland" <dba_at_remove_spam.peasland.com> wrote in message
> news:3F560FCA.BEB646C4_at_remove_spam.peasland.com...
> > > ALTER SYSTEM ARCHIVE LOG STOP;
> >
> > As Daniel pointed out, there is a difference between logging and
> > archiving. This stops the archiving, but not the logging. If your only
> > wish is to stop the excessive archiving then this will work. But the
> > side effect is that you won't be able to fully recover your database
> > from the previous backup. Not what I'd want to do. As I've already said,
> > the tool to use is NOLOGGING and a Direct path load in SQL*Loader. With
> > this option, you can still recover your database. You just won't be able
> > to recover the load operation that you performed. Big difference!!!
> >
> > HTH,
> > Brian
> >
> >
> >
> >
> > --
> > ===================================================================
> >
> > Brian Peasland
> > dba_at_remove_spam.peasland.com
> >
> > Remove the "remove_spam." from the email address to email me.
> >
> >
> > "I can give it to you cheap, quick, and good. Now pick two out of
> > the three"

-- 
===================================================================

Brian Peasland
dba_at_remove_spam.peasland.com

Remove the "remove_spam." from the email address to email me.


"I can give it to you cheap, quick, and good. Now pick two out of
 the three"