That's what happens when you write posts at 4.00am. You miss juicy little
bits like that.... but, of course, if it's an update, the redo involved will
be trivially small in comparison to what an insert would generate, anyway.
Regards
HJR
--
----------------------------------------------
Resources for Oracle: http://www.hjrdba.com
===============================
"Igor Ushkalo" <igorus_at_protek.ru> wrote in message
news:a2bubn$l65$1_at_news.sovam.com...
> Hello, Howard!
> You wrote on Sun, 20 Jan 2002 00:29:58 +1100:
>
> HJR> You can switch that off without having to disable archivelog mode
> HJR> itself merely by altering the relavant table to be 'NOLOGGING' -and
> HJR> then making sure that this bulk insert is being done by SQL Loader.
> HJR> If it's just a conventional 'insert' statement you're doing then
> HJR> NOLOGGING won't do anything for you at all. Otherwise, it will
> HJR> switch off the generation of all redo -and since nothing is getting
> HJR> into the online logs, you worries about its impact on ARCH will be
> HJR> sorted at the same time.
>
> But it seems he wants UPDATE table... i dunno any way
> to do update in nologging mode.
>
> Maybe you can get some perfomance gain to switch to noarchivelog
> if all of your redo-logs are on the same device (mirror); but if logs are
> situated on
> two mirrors (even/odd logs on different mirrors) - archiver won't be a
> problem...
>
> -- Best regards, Igor Ushkalo (igorus!) - igorus(at)mail.ru, ICQ #19972198
>
>
Received on Sat Jan 19 2002 - 16:07:36 CST
