Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: beq processes preventing shutdown
Paul,
My guess is that these are orphaned connections (a user killed his sqlplus connection and the unix network process did not go away).
You could, as part of the shutdown performed by your sysadmin, include a simple script that produces a report of all sessions that are currently connected to the database. Query the v$session view. A simple report using the query below would give you the information regarding who is connected when the shutdown is being attempted:
SELECT username,server,status,osuser,machine,terminal, program,
TO_CHAR(logon_time,'mm/dd/yyyy hh24:mi:ss')
FROM v$session
WHERE username IS NOT NULL
PS - is your sysadmin performing a SHUTDOWN IMMEDIATE or a SHUTDOWN?
A SHUTDOWN waits for all connected processed to disconnect, while a SHUTDOWN IMMEDIATE terminates all connected processes and shuts the db down.
Good luck!
Tom Mercadante
Oracle Certified Professional
-----Original Message-----
Sent: Tuesday, May 27, 2003 10:40 AM
To: Multiple recipients of list ORACLE-L
Paul - So you are saying that shutdown immediate doesn't? I had this happen awhile back and most suggestions were that there was a process that wasn't ever going idle. Check your alert log for the following message:
SHUTDOWN: waiting for active calls to complete The posters suggested that I would probably end up doing what you are suggesting. In my case the problem hasn't recurred yet.
Dennis Williams
DBA, 80%OCP, 100% DBA
Lifetouch, Inc.
dwilliams_at_lifetouch.com
-----Original Message-----
Sent: Tuesday, May 27, 2003 7:40 AM
To: Multiple recipients of list ORACLE-L
Our sysadmin tells me he's been experiencing problems sometimes, when trying to shutdown an Oracle 8.1.7 instance on a Solaris 64-bit environment. The shutdown "hangs up", and he can see processes like the following:
oraclePROD (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))
>From searching around, I've been able to ascertain that these "beq" processes are probably created by the listener in response to connect requests, but beyond that, I'm stumped!
All I've been able to advise is that he replace his "shutdown immediate" with a 3-step "shutdown abort / startup restrict / shutdown immediate" sequence, which should prevent being hung up by any "beq processes", but I'd rather feel I'd solved the problem, rather than merely sidestepping it!
Any ideas what may be causing this, and what the remedy might be?
Regards,
Paul Vincent
DBA
University of Central England
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Paul Vincent
INET:
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).
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).
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 May 27 2003 - 11:09:54 CDT