I bet you can get that 4 minutes down to 1 if you dispense with the
down/up/down and just do checkpoint/abort/failover/startup.
Why bother with "immediate" for a cluster failover? Isn't it just a
waste of time?
--
Jeremiah Wilton
http://www.speakeasy.net/~jwilton
On Tue, 21 Oct 2003, Tortorelli, Mary Jo wrote:
> An 8.1.7.4 production database on HP-UX 11.0 running Apps 11.5.7 takes long to shutdown and is causing cluster failover testing to time out.
>
> Upon shutdown immediate it takes 1-3 minutes for the DATABASE DISMOUNTED, DATABASE CLOSED, and Archival stopped messages in the alert log but then it takes another 15+ minutes for the ORACLE database shutdown message to return to sqlplus. During this time, a ps -ef shows no background or ghost database processes - only the sqlplus process.
>
> If a shutdown abort, startup restrict, shutdown is done after five minutes, the shutdown after the abort/startup takes 4 minutes total.
>
> Does anyone know what Oracle does between DATABASE CLOSED, ARCHIVE STOPPED and the ORACLE database shutdown message? Has anyone else run into this?
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Jeremiah Wilton
INET: jwilton_at_speakeasy.net
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 Tue Oct 21 2003 - 18:24:25 CDT
