Home » RDBMS Server » Performance Tuning » SQL*Net Message from client
SQL*Net Message from client [message #64866] Sat, 21 February 2004 02:54 Go to next message
Joe Fabiano
Messages: 1
Registered: February 2004
Junior Member
I turned sql tracing on by executing:

alter session set events '10046 trace name context forever, level 8'

Then executed: select sysdate from dual;

8 hours later within the same session I execute:

select sysdate from dual;

Then I disconnected and ran tkprof with waits=yes option.  I was surprised that the

SQL*Net Message from client wait showed only 21 minutes. I would have expected an  8 hour elsapse time.  Any ideas?
Re: SQL*Net Message from client [message #64868 is a reply to message #64866] Mon, 23 February 2004 01:10 Go to previous messageGo to next message
Frank Naude
Messages: 4578
Registered: April 1998
Senior Member

Maybe there were some communications between the client and DB. For example, when using DCD (Dead Connection Detection). View your SQLNET.ORA file to see if you've set SQLNET.EXPIRE_TIME.

When DCD is used, the server will "probe" the client every SQLNET.EXPIRE_TIME minutes to see if it is still there.

Best regards.

Re: SQL*Net Message from client [message #64870 is a reply to message #64866] Mon, 23 February 2004 08:50 Go to previous message
Messages: 1089
Registered: May 2002
Senior Member
just curious,did you also check the wait time,max_wait time in v$session_event ? do they match?
Previous Topic: Very slow wildcard query
Next Topic: buffer cache hit ratio reduces to -3
Goto Forum:

Current Time: Sat Feb 24 20:04:30 CST 2024