Home » RDBMS Server » Networking and Gateways » SQL*Net message from client (Oracle, 9.2.0.8, sunos)
SQL*Net message from client [message #571255] Thu, 22 November 2012 09:13 Go to next message
savugar
Messages: 33
Registered: February 2012
Member
Hi,

I am seeing the below sessions in v$session_wait. When I was trying to understand the value of P1,P1text,P1RAW, I got the below information.

P1RAW = 0x54435000 = 'TCP\0'
P1TEXT = 1413697536 = TCP



But I cannot able to understand this. What it says? Can I say these session are waiting due to network slowness? But all the time I am seeing these many sessions on SQL*Net message from client. in this case, can I say my netwrok buffer size is very low? Pls help



   SID EVENT           P1TEXT               P1 P1RAW            P2TEXT               P2 P3TEXT       P3  WAIT_TIME SECONDS_IN_WAIT STATE
------ --------------- ------------ ---------- ---------------- ------------ ---------- ------------ ---------- ---------- --------------- ----------
-
    94 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1                   0      0               3 WAITING
        from client

   254 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0               3 WAITING
        from client

   234 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0               3 WAITING
        from client

   294 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0               3 WAITING
        from client

   165 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0              16 WAITING
        from client

   305 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0              18 WAITING
        from client

   283 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0              24 WAITING
        from client

   286 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0              44 WAITING
        from client

    80 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1                   0      0              53 WAITING
        from client

   221 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0              81 WAITING
        from client

   153 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0              86 WAITING
        from client

   194 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0             102 WAITING
        from client

   179 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0             110 WAITING
        from client

   310 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0             156 WAITING
        from client

   259 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0             167 WAITING
        from client

    12 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1                   0      0             171 WAITING
        from client

    66 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1                   0      0             177 WAITING
        from client

   171 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0             190 WAITING
        from client

   189 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0             225 WAITING
        from client

   247 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0             235 WAITING
        from client

   120 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0             237 WAITING
        from client

   195 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0             239 WAITING
        from client

   267 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0             258 WAITING
        from client

   279 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0             517 WAITING
        from client

   197 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0             780 WAITING
        from client

    61 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1                   0      0             781 WAITING
        from client

    77 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1                   0      0            6406 WAITING
        from client

   175 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0          0            6505 WAITING
        from client

   200 SQL*Net message driver id    1413697536 0000000054435000 #bytes                1               0         -1               0 WAITED KNOWN TIME
        to client
Re: SQL*Net message from client [message #571256 is a reply to message #571255] Thu, 22 November 2012 09:19 Go to previous messageGo to next message
John Watson
Messages: 4562
Registered: January 2010
Location: Global Village
Senior Member
Those sessions are waiting for the client to ask them to do something. Look at v$event_name and you'll see that the wait event is in the "Idle" class.
Re: SQL*Net message from client [message #571257 is a reply to message #571256] Thu, 22 November 2012 09:23 Go to previous messageGo to next message
BlackSwan
Messages: 22790
Registered: January 2009
Senior Member
It appears that you suffer from Compulsive Tuning Disorder.
Why do you go looking for problems that only exist between your ears?
Re: SQL*Net message from client [message #571258 is a reply to message #571256] Thu, 22 November 2012 09:32 Go to previous messageGo to next message
savugar
Messages: 33
Registered: February 2012
Member
Yes I agree. Though it is an Idle waitevent, I feel it is better to look on this area, since we are having many sessions on this area most of the times. And also all the session are having the same P1,P1text &P1RAW value. That's why I am trying to understand the issue here.

[Updated on: Thu, 22 November 2012 09:33]

Report message to a moderator

Re: SQL*Net message from client [message #571259 is a reply to message #571258] Thu, 22 November 2012 09:38 Go to previous messageGo to next message
savugar
Messages: 33
Registered: February 2012
Member
Hi Blackswan,

We are having High CPU utilization issue. Average CPU utilization is around 40% and Some time it is crossing 90%. But there is no much active sessions (only 1 or 2 sessions) during 40% utilization. only I am seeing lot of INACTIVE sessions (around 40). That's why I am analyzing these things.
Re: SQL*Net message from client [message #571270 is a reply to message #571259] Thu, 22 November 2012 14:47 Go to previous messageGo to next message
BlackSwan
Messages: 22790
Registered: January 2009
Senior Member
>We are having High CPU utilization issue.
Why blame it on Oracle?
Re: SQL*Net message from client [message #571277 is a reply to message #571270] Thu, 22 November 2012 21:59 Go to previous messageGo to next message
savugar
Messages: 33
Registered: February 2012
Member
because it is database server. So most of the processes are oracle process and that only consuming high cpu's
Re: SQL*Net message from client [message #571278 is a reply to message #571277] Thu, 22 November 2012 22:24 Go to previous messageGo to next message
BlackSwan
Messages: 22790
Registered: January 2009
Senior Member
WAITING & INACTIVE sessions do *NOT* consume CPU cycles
Re: SQL*Net message from client [message #571285 is a reply to message #571278] Fri, 23 November 2012 00:16 Go to previous messageGo to next message
savugar
Messages: 33
Registered: February 2012
Member
But some time I am seeing these sessions are consuming CPU's bucasue it becomes ACTIVE and getting INACTIVE immediately. This might be a reason for this I guess. Anyway these sessions are in WAITING status. The reason may be due to network issue or poor application code. Now what I need to check to find out why these sessions are waiting? Pls help
Re: SQL*Net message from client [message #571299 is a reply to message #571285] Fri, 23 November 2012 01:48 Go to previous message
John Watson
Messages: 4562
Registered: January 2010
Location: Global Village
Senior Member
Quote:
Now what I need to check to find out why these sessions are waiting? Pls help
I've already told you! They are WAITING because they have nothing to do.
Previous Topic: TNS:operation timed out
Next Topic: Heterogeneous database integrated
Goto Forum:
  


Current Time: Fri Sep 19 01:51:22 CDT 2014

Total time taken to generate the page: 0.32322 seconds