Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: 9i shared servers (dispatcher) hung

RE: 9i shared servers (dispatcher) hung

From: Powell, Mark D <mark.powell_at_eds.com>
Date: Wed, 31 Aug 2005 13:58:34 -0400
Message-ID: <5A14AF34CFF8AD44A44891F7C9FF41050395BA72@usahm236.amer.corp.eds.com>


According to the manual the dispatcher does not shutdown until all the processes it was running are cleaned up so did you check to see if a ROLLBACK was in progress?  

HTH -- Mark D Powell --  


From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Jeffrey Beckstrom Sent: Wednesday, August 31, 2005 1:44 PM To: oracle-l_at_freelists.org; oracle-db-l_at_Groups.ITtoolbox.com; ORACLE-L_at_IC.SUNYSB.EDU; oracledba_at_LazyDBA.com; oracle-rdbms_at_yahoogroups.com
Subject: 9i shared servers (dispatcher) hung

People could not connect via shared server - hung. So tried stopping the dispatchers and restarting them. I did:
alter system shutdown immediate 'D000' ; alter system shutdown immediate 'D001' ;

In alert log I see the following.
idle dispatcher 'D000' terminated, pid = (13, 1)

I do not see d001 stopping. If do a lsnrctl services it still shows d001.

If do:
ALTER SYSTEM SET DISPATCHERS=''(address=(host=10.20.7.11)(proto =tcp))(dispatchers=2)'';

Then lsnrctl services shows d000, d001 and d002.

I ended up bouncing the database. I had to do a shutdown abort since shutdown immediate hung - probably due to dispatcher d001 getting stuck. Any ideas on why a dispatcher would get stuck?      

Jeffrey Beckstrom
Database Administrator
Greater Cleveland Regional Transit Authority 1240 W. 6th Street
Cleveland, Ohio 44113

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Aug 31 2005 - 13:01:05 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US