Re: NOLOGGING option

Taking the database out of archivelog mode doesn't reduce logging, it just stops the log files from being copied.

Regarding volume of redo - try setting

    transaction_auditing=false
in the init.ora.

The parameter does not work as documented in the 8.1 manuals, and generates an large "audit change vector" in the redo log for every transaction that a session starts. If you have large numbers of single row commits (which you shouldn't, of course) and your machine names, program names etc. are
quite long, you could find that 30% of your log file is transaction auditing that you never intend to use.

This is ameliorated in 9.1, where only the first "audit change vector" of a session is a full vector, and subsequent ones are much smaller.

--
Jonathan Lewis
http://www.jlcomp.demon.co.uk

Author of:
Practical Oracle 8i: Building Efficient Databases

Next Seminar - Australia - July/August
http://www.jlcomp.demon.co.uk/seminar.html

Host to The Co-Operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html



Bob Bain wrote in message ...


>

>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??

>