found dead dispatcher, every morning at 2 am 9.2.0.4/win32
- From: Paul Drake <discgolfdba@xxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Thu, 10 Jun 2004 09:15:10 -0700 (PDT)
I've got this system that has a pair of dispatchers
that apparently die right after last call (2 am).
Event logs show nothing anywhere near that time.
No scheduled tasks then.
No dbms_job scheduled for then.
Metalink doesn't return anything recent, nothing in
9.2. The ora-600 tool comes up empty for the call
stack trace search.
"found dead dispatcher 'D0002', pid = (18, 191)
found dead dispatcher 'D0002', pid = (19, 104)"
no trace file is generated at that time.
Has anyone running shared servers had dispatchers
dying same time every day?
the 2 am thing is not a big deal, but a combination of
a dispatcher and shared server has now been dumping
state level 10 intermittently during the day, which is
a bigger deal.
the only reason that this system has
dispatchers/shared servers is due to the VPN policy
used to access that site, so dedicated server
processes over random ports is not an option. app
users are connecting to dedicated sessions.
found some interesting bits of text in the trace file,
such as "Internal Review". I know, sounds like a bug
and I should file an iTAR. Just thought that I'd see
if anyone else had hit this.
Paul
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
- » found dead dispatcher, every morning at 2 am 9.2.0.4/win32
