Re: Disable logging in tablespace vs using hidden parameter _disable_logging

Just as a side note, unless things have change in recent versions, _disable_logging still does all the work of generating redo log.

The only change is that lgwr doesn't bother to write the buffer when called - basically bypassing the actual file-write call.

This means you still get redo latch activity, and checkpoints. Given the fact that lots of systems now have a workable buffer between the redo writer and the hardware, this means that _disable_logging may give you no appreciable benefit, unless you create MASSIVE redo log and avoid commits.

Regards

Jonathan Lewis

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

http://www.jlcomp.demon.co.uk/cbo_book/ind_book.html Cost Based Oracle: Fundamentals

http://www.jlcomp.demon.co.uk/appearances.html Public Appearances - schedule updated 10th Jan 2006

• Original Message ----- From: "Bobak, Mark" <Mark.Bobak_at_il.proquest.com> To: <juancarlosreyesp_at_gmail.com>; "Li-Shan Cheng" <exriscer_at_gmail.com> Cc: <oracle-l_at_freelists.org> Sent: Thursday, February 02, 2006 6:53 PM Subject: RE: Disable logging in tablespace vs using hidden parameter
  _disable_logging
  

_disable_logging, on the other hand, says "I don't care about this
database, don't do any logging, if the database crashes, it's worthless, game reset, start over." This is quite different from, and far more dangerous than, NOLOGGING operations.

Hope that helps,

-Mark

--
Mark J. Bobak
Senior Oracle Architect
ProQuest Information & Learning

"There are 10 types of people in the world:  Those who understand
binary, and those who don't."


--
http://www.freelists.org/webpage/oracle-l