The scenario you describe would occur regardless of the archive mode. An active log cannot be archived. This would require that the ARCH process read the log while LGWR is writing it. Once a log switch occurs (automatic or manual), the previously active log can be archived.
In this scenario, you cannot perform a complete recovery. You can recover up to the last log that can be read. If the active log cannot be read, the previous log is the end point of your recovery.
-- 
Daniel W. Fink
http://www.optimaldba.com

IOUG-A Live! April 27 - May 1, 2003 Orlando, FL
   Sunday, April 27 8:30am - 4:30pm - Problem Solving with Oracle 9i SQL
   Thursday, May 1 1:00pm - 2:00pm - Automatic Undo Internals

GovindanK wrote:
This topic is getting interesting once more. Lets contribute.

  
Multiplexing redo logs has nothing to do with the archive mode.
      

Take a situation wherein the db is in NOARCH mode with only one member per group (default setup).  The dba gives shutdown abort and upon starting for some reason the active log could not be read for recovery. How would one perform a complete recovery?. 

Let me know if you have a workaround. 

I am willing to learn.

GovindanK
  






Reply via email to