Return-Path: Received: from newsfeed.cts.com (newsfeed.cts.com [209.68.248.164]) by naude.co.za (8.11.2/8.11.2) with SMTP id g787qJc24281 for ; Thu, 8 Aug 2002 03:52:19 -0400 Received: from fatcity.UUCP (uucp@localhost) by newsfeed.cts.com (8.9.3/8.9.3) with UUCP id AAA76782; Thu, 8 Aug 2002 00:52:15 -0700 (PDT) Received: by fatcity.com (26-Feb-2001/v1.0g-b71/bab) via UUCP id 004AEA6F; Thu, 08 Aug 2002 00:13:20 -0800 Message-ID: Date: Thu, 08 Aug 2002 00:13:20 -0800 To: Multiple recipients of list ORACLE-L X-Comment: Oracle RDBMS Community Forum X-Sender: "Sinardy Xing" Sender: root@fatcity.com Reply-To: ORACLE-L@fatcity.com Errors-To: ML-ERRORS@fatcity.com From: "Sinardy Xing" Subject: RE: unable to shutdown immediate Organization: Fat City Network Services, San Diego, California X-ListServer: v1.0g, build 71; ListGuru (c) 1996-2001 Bruce A. Bergman Precedence: bulk Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by naude.co.za id g787qJc24281 There is bug 8.1.6 with archivelog mode (shutdown immediate hang) -----Original Message----- Sent: 08 August 2002 06:16 To: Multiple recipients of list ORACLE-L I am resubmitting this email, as it didn't seem to show up after it was originally sent last night and this morning. Last night I was planning to do a quick bounce of the database, and get our 24x7 shop right back online. Problem was I wasn't able to complete a 'shutdown immediate'. I went through each of the existing sessions in v$session and made sure that all of the user sessions were killed or inactive, but the shutdown immediate still wouldn't process. With damagement standing there looking worried, I went ahead with a shutdown abort just so we could get back to online processing. This is a relatively new phenomenom for me, as shutdown immediate or killing user sessions has almost always worked for me in the past. I will add that while I was away on vaca tion last week, my standin had to do two shutdown aborts of the database. So something might just be amiss. Anyhow My question is what should I look for when an instance won't shutdown via a shutdown immediate? Or maybe my problem is that I should just wholeheartedly embrace shutdown abort, and just let the recovery process clean things up. My problem with that is I used to work with a senior dba that would slap my wrist with a ruler, if I shutdown abort. Steve McClure -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Steve McClure INET: smcclure@usscript.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@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.com -- Author: Sinardy Xing INET: SinardyXing@bkgcomsvc.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@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).