Re: Transaction without redolog

_disable_logging does all the processing that normally gets done, except for the actual call to write to the log file - so checkpoints and log-switches do occur, which explains your sequence numbers.

There are just a few writes (file header information) that still gets written and checked as each file is (notionally) acquired on the log switch.

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

Now running 3-day intensive seminars
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

Author of:
Practical Oracle 8i: Building Efficient Databases


John Darrah wrote in message
<36381c83d490f2e8d992e56374c5ed52.36240_at_mygate.mailgate.org>...


>Howard,

>

>I am running an import on a dev DB with the _disable_logging parameter set

to


>true.  Before anyone scolds me, yes I have backups.  My question is when I

>query the v$log table the sequence#s are still being incremented.  Also,

the


>modification dates on the redo logs themselves seem to be changing.  I know

>that this parameter does do something because I've set it, done a shutdown

>abort and the db did end up corrupt.  I'm wondering why exactly the

sequences


>would be incrementing and what is getting written to the actual log files.

My


>guess is

>it probably writing something like "don't even bother trying to use this

log


>for recovery purposes" but was wondering if you or anyone else had a

definative


>answer.