"Bob Bain" <bob.bain_at_markelintl.com> wrote in message
news:Slwx8.253$jE.2609_at_news.uk.colt.net...
> Hi,
>
> NOLOGGING is such a great misnomer isn't it.
>
> We thought this would be the answer to all our questions but unfortunately
> it ain't, the only way to get around this (that I know, flame me if I'm
> wrong) is to take the database out archive redo mode, do your updates and
> then put it back in.....
>
> BTW have you noticed that the amount of redo generated in 8i is massive
> compared to earlier versions??
>
> Cheers
>
> Bob
Depends what your 'problem' is. If the problem is that your archive log
destination is filling too rapidly then your suggestion will 'fix' that
problem at the expense of recoverability. If on the other hand the problem
is with the redo IO then your 'fix' will lose recoverability and make no
difference at all to redo IO.
--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer
******************************************
Received on Wed Apr 24 2002 - 06:57:03 CDT
