| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Shutdown takes 20+ minutes
Jeremiah and Jared,
Big thanks for your comments. I was going down the path of trying to figure out the cause versus just solving the problem. I understand from a co-worker there was a huge thread on shutdown abort before I got on this listserver. Appreciate the info again! Now I just have to convince mgmt it's OK.
Mary Jo
-----Original Message-----
Sent: Wednesday, October 22, 2003 3:20 PM
To: Multiple recipients of list ORACLE-L
Uh-oh. I'm sure Jeremiah is digging up some old posts for cut and paste to avoid typing.
Here, I'll save him the trouble.
I would submit that ABORT is one of the most tested features of Oracle 8 and 9 - not at Oracle, but at customer sites - because it is one of the most used. No serious HA site is still using IMMEDIATE on a consistent basis, because it is unreliable. Consistent performance requires the use of ABORT for reliable shutdowns and for cluster failovers. Oracle even recommends it in their FailSafe manual.
So my advice is to cite the exact circumstances, test case and number of your bug for those few still using version 7. Many features were screwed in V.7. I would submit that in your case, with an unresponsive instance, you may have had problems outside your database that contributed to the need for recovery, and are mistakenly fingering ABORT as the cause. Since Oracle 7.3.4, I have not heard reliable accounts of any problems with ABORT. This is mainly because transactions are transactions, and they have to have a response from the O/S and recorded their redo before a COMMIT is returned to the application. That makes them recoverable as soon as they are considered successful by the app.
"Tortorelli, Mary Jo" <tortorelli_at_ppg.com> Sent by: ml-errors_at_fatcity.com
10/22/2003 09:44 AM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com>
cc:
Subject: RE: Shutdown takes 20+ minutes
Jeremiah,
We do shutdown immediate as the standard weekly cycle/cold-backup of this production db. The cluster failover is part of the procedure and is a test - it's not a real failover. We don't want to routinely shutdown abort and increase corruption potential if it's not necessary.
We want a clean shutdown for the backup and I'm trying to figure out why it takes so long since it's messing up the fail-over test that follows.
-----Original Message-----
Sent: Tuesday, October 21, 2003 7:24 PM
To: Multiple recipients of list ORACLE-L
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:Received on Thu Oct 23 2003 - 09:34:26 CDT
> 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). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Tortorelli, Mary Jo INET: tortorelli_at_ppg.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). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Tortorelli, Mary Jo INET: tortorelli_at_ppg.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).
 |
 |