Re: NOLOGGING option

From: Bob Bain <bob.bain_at_markelintl.com>
Date: Wed, 24 Apr 2002 12:05:37 -0000
Message-ID: <Slwx8.253$jE.2609@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

"Steven" <steven.pannell_at_gmx.net> wrote in message news:aa5spe$7ui0d$1_at_ID-82797.news.dfncis.de...
> Hi,
>
> I have an update statement which selects and updates some 300,000 rows of
> data. Even though I have the NOLOGGING option enabled on the table and
> tablespace i have noticed that the data is still been written to the redo
> logs, this causes a high level of log switching. Is there any way to
> disable the logging and writing of data to the redo logs as the NOLOGGING
> option does not seem to work in the way I would like.
>
> I'm using Oracle 8.1.7 on Solaris.
>
> Thanks,
> Steve.
>
>
>
Received on Wed Apr 24 2002 - 07:05:37 CDT