RE: 9i shared servers (dispatcher) hung

  • From: "Gogala, Mladen" <MGogala@xxxxxxxxxxxxxxxxxxxx>
  • To: "'JBECKSTROM@xxxxxxxxx'" <JBECKSTROM@xxxxxxxxx>, oracle-l@xxxxxxxxxxxxx, oracle-db-l@xxxxxxxxxxxxxxxxxxxx, ORACLE-L@xxxxxxxxxxxxx, oracledba@xxxxxxxxxxx, oracle-rdbms@xxxxxxxxxxxxxxx
  • Date: Wed, 31 Aug 2005 14:20:46 -0400

Internal deadlock, possibly? Sounds like a situation for hanganalyze
utility. There is a little article mentioning

hanganalyze at



Mladen Gogala

Ext. 121


From: Jeffrey Beckstrom [mailto:JBECKSTROM@xxxxxxxxx] 
Sent: Wednesday, August 31, 2005 1:44 PM
To: oracle-l@xxxxxxxxxxxxx; oracle-db-l@xxxxxxxxxxxxxxxxxxxx;
ORACLE-L@xxxxxxxxxxxxx; oracledba@xxxxxxxxxxx; oracle-rdbms@xxxxxxxxxxxxxxx
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:

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

Other related posts: