| 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:RE: unable to shutdown immediate
Just my $.02. Everytime, one of my databases failed to shutdown immediate where a shutdown abort worked was b/c of dbms_jobs. If I turned it off (job_queue_processes=0), shutdown immediate worked. BTW, this was an occassional occurrence and on 7.3 db's. One of the reasons I prefer cron for scheduling jobs.
hth,
Gene
>>> dgoulet_at_vicr.com 08/08/02 02:13PM >>> Steve,
I have seen a shutdown immediate "hang" before and every once in a while now as well. Each time I've checked the HP system and found it 100% idle which is perplexing. Also if you look for the background processes the only one up is PMON and/or SMON. Kinda strange so I called Oracle. The tech at OTS explained it this way:
A shutdown immediate first waits for any open transaction to complete. If the transaction is open (namely no rollback or commit has been issued) and the session is idle then the DB will rollback the transaction for the user and attempt to send them a message to that effect. This does work very well with sessions that are connected to the database and someone or thing is there responding. The problem occurs with sessions that have been killed and/or given the MicroSoft three finger salute (CTRL-ALT-DEL). In this case the session has nothing on the other end of that tcp/ip connection that is listening. This is a very prevalent condition with WEB servers, especially those using certain versions of MicroSoft's ODBC drivers. In this case PMON attempts to complete the communication between the client and server, but since there is no one listening it takes several minutes before it gives up. Hence the appearance of a hang. They suggest having some patience or using shutdown abort.
Dick Goulet
____________________Reply Separator____________________ Author: "Steve McClure" <smcclure_at_usscript.com> Date: 8/8/2002 9:48 AM
Thanks all,
and sorry for spamming the list. After my first message didn't make it through I got response from the list server that it had filtered my message because it looked like an automated reply(I had included the word v a c a t i o n in my original, and so thought I had hit a filter. SO I did the natural thing and tried different phrases every hour or so till my message got through, about 4 times now =).
I always forget about startup force, maybe I will give that a try. I almost always alter system checkpoint before an abort. I need to update my documentation, so others will do so as well if I am away again.
Thanks again,
Steve McClure
-----Original Message-----
Sent: Thursday, August 08, 2002 3:33 AM
To: Multiple recipients of list ORACLE-L
There is also a bug (so far in all versions) that sometimes shows up. Search on EMN0 (search in your alert logs and in metalink). There are a lot of hits on it, and we have found one of our instances doing this... it hangs in shutdown immeidate. Oracle solution... Shutdown Abort, startup restrict, shutdown immediate...and they repeat (A LOT) that this is a valid solution to the problem...
ajw
-----Original Message-----
To: Multiple recipients of list ORACLE-L
Sent: 8/8/02 3:13 AM
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_at_usscript.com
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Liststo: 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).
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Liststo: 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).
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Steve McClure
INET: smcclure_at_usscript.com
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Liststo: 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).
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Liststo: 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).
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Liststo: 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 Thu Aug 08 2002 - 13:39:26 CDT
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
 |
 |