Re: How much time can save using _disable_logging on 10g

  • From: Tanel Põder <tanel.poder.003@xxxxxxx>
  • To: "ORACLE-L" <oracle-l@xxxxxxxxxxxxx>
  • Date: Wed, 23 Nov 2005 19:38:42 -0600

Hi,

The question is:
Is the trick to do a log switch and a shutdown normal , or situation
unpredictable like this are typical, I mean the redologs can appear
corrupt.
My theory is that a normal shutdown should be enough.
Is there some trick,or this is only a coincidence, and I shouldn't get
this corruption in logs.

You could try alter database clear logfile group 1, group 2, group x; before starting up the database with enabled logging again.
I think it was 9.2 or 10r1 in some platform which crashed during startup when _disable_logging was set to true so you must be very careful (several thorough tests) before doing anyting in disable logging mode. Especially now when Oracle has done lots of changes to redologging mechanisms (multiple redo strands, private redo strands etc).

As an alternative you could leave those parameters as they are and temporarily move your redologs (noarchivelog mode) onto a RAM filesystem - although this configuration is probably unsupported as well...

Tanel.

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


Other related posts:

  1. Home
  2. oracle-l
  3. Archive
  4. 11-2005