Not sure I am correct, but this looks like DCD (Dead Connection
Detection) in action. If you have SQLNET.EXPIRE_TIME non-zero
in SQLNET.ORA on the server, then this trace probably means that
DCD detected a dead (ungracefully terminated) client and SMON
kicked in to clean up the session.
Of course, I may be wrong here, you may contact Oracle Support
and ask them to explain this trace to be sure.
--
Vladimir Zakharychev (bob@dpsp-yes.com) http://www.dpsp-yes.com
Dynamic PSP(tm) - the first true RAD toolkit for Oracle-based internet applications.
All opinions are mine and do not necessarily go in line with those of my employer.
"Alex" <a.jens_at_sigmasoft.cz> wrote in message
news:2c98baa9.0210212248.38599808_at_posting.google.com...
> Hi,
>
> sometimes I have got this message in SMON trace file:
>
> *** 2002-10-21 14:51:30.000
> *** SESSION ID:(11.213) 2002-10-21 14:51:30.000
> Probe:read_pipe: receive failed, status 3
> Probe:S:debug_loop: timeout. Action 1
>
>
> RDBMS config. is:
> Oracle9i Release 9.0.1.1.1 - Production
> JServer Release 9.0.1.1.1 - Production
> Windows 2000 Version 5.0 Service Pack 2, CPU type 586
>
> Can you tell me where is the problem or what does it mean ?
>
> Thanks Alex
Received on Tue Oct 22 2002 - 04:54:06 CDT
