Re: FastStart Failover Problem.

From: <Laimutis.Nedzinskas_at_seb.lt>
Date: Tue, 5 Aug 2014 08:51:46 +0300
Message-ID: <OFFC9378AD.3EE77F2B-ONC2257D2B.001FD69C-C2257D2B.002034F2_at_seb.lt>


This is the strength of Oracle dedicated process architecture. Some user processes might die but the others will work and may be your last opportunity to remedy the situation (export critical data for example.)

Brgds, Laimis N


Please consider the environment before printing this e-mail

From:	"MacGregor, Ian A." <ian_at_slac.stanford.edu>
To:	"oracle-l_at_freelists.org" <oracle-l_at_freelists.org>,
Date:	2014.08.05 01:42
Subject:	FastStart Failover Problem.
Sent by:	oracle-l-bounce_at_freelists.org



We’ve been running FastStart Failover for quite a while, and it has served us well. However we had an interesting problem a couple of weeks ago. The primary server panicked but got stuck on the way down. It entered a state where it was not accepting any new connections either via sql*net or ssh. However, existing connections were not closed. Thus dataguard saw the primary database as being up. Even though no one could connect to it.

Ian MacGregor
SLAC National Laboratory--
http://www.freelists.org/webpage/oracle-l



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


graycol.gif
Received on Tue Aug 05 2014 - 07:51:46 CEST

Original text of this message