Archival Freeze

From: <Rajesh.Rao_at_jpmchase.com>
Date: Fri, 12 Apr 2002 13:13:23 -0800
Message-ID: <F001.004439E8.20020412131323@fatcity.com>

Hi Fellow DBAs,

I and a fellow DBA are currently debating about how insufficient space in the archive destination freezes up the DB. He claims that as soon as the ARCH process is unable to write to the disk, the db freezes. I am of the opinion that it does not. It will only report an error (Any idea, what the error code is?). It will only freeze when it cycles thru the rest of the redolog groups, and then when it tries to switch log to the one which has not been archived. That's why the error message is "cannot allocate new log".

Whats your say? He's also on this list.

Raj

--

Please see the official ORACLE-L FAQ: http://www.orafaq.com
--

Author:
  INET: Rajesh.Rao_at_jpmchase.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------

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 Fri Apr 12 2002 - 16:13:23 CDT