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
>
>
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Daniel W. Fink
INET: optimaldba_at_yahoo.com
Fat City Network Services -- 858-538-5051 http://www.fatcity.com
San Diego, California -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
Received on Wed Apr 02 2003 - 15:13:45 CST
