SQL*Net message from client high wait time

[Roshan]

Hello Erman,

I have enabled tracing on my DB (19.3) OS RHEL 8.

I see the highest wait time is SQL*Net message from client  . I do not see any high elapsed time for sql queries. Do you think network team should intervene or is it a bug in application?


Misses in library cache during parse: 0
Optimizer mode: CHOOSE
Parsing user id: SYS   (recursive depth: 1)
Number of plan statistics captured: 1

Rows (1st) Rows (avg) Rows (max)  Row Source Operation
---------- ---------- ----------  ---------------------------------------------------
         1          1          1  TABLE ACCESS BY INDEX ROWID BATCHED OBJ$ (cr=4 pr=0 pw=0 time=30 us starts=1 cost=1 size=43 card=1)
         1          1          1   INDEX RANGE SCAN I_OBJ1 (cr=3 pr=0 pw=0 time=21 us starts=1 cost=1 size=0 card=1)(object id 36)




********************************************************************************

OVERALL TOTALS FOR ALL NON-RECURSIVE STATEMENTS

call     count       cpu    elapsed       disk      query    current        rows
------- ------  -------- ---------- ---------- ---------- ----------  ----------
Parse    23691      0.33       0.37          0          0          0           0
Execute  23690      3.35       4.31         42       2907      16100        1490
Fetch    22610     56.08     110.38      19616     321468       3085       59840
------- ------  -------- ---------- ---------- ---------- ----------  ----------
total    69991     59.77     115.06      19658     324375      19185       61330

Misses in library cache during parse: 1
Misses in library cache during execute: 2

Elapsed times include waiting on following events:
  Event waited on                             Times   Max. Wait  Total Waited
  ----------------------------------------   Waited  ----------  ------------
  SQL*Net message to client                   30898        0.00          0.04
  PGA memory operation                          143        0.00          0.00
  SQL*Net message from client                 30898      234.37        594.89
  log file sync                                 240        0.01          1.21
  library cache: mutex X                        843        0.02          2.12
  Disk file operations I/O                      238        0.00          0.00
  asynch descriptor resize                        1        0.00          0.00
  ASM IO for non-blocking poll                32848        0.00          0.04
  direct path read                            16330        0.08         28.31
  SQL*Net more data to client                 23348        0.01          0.60
  db file sequential read                      1703        0.04          3.66
  latch: object queue header operation           17        0.01          0.04
  SQL*Net break/reset to client                   8        0.00          0.00
  row cache mutex                                46        0.01          0.07
  SQL*Net more data from client                  80        0.00          0.00
  SQL*Net vector data to client                   1        0.00          0.00

[ErmanArslansOracleBlog]

It is an idle event.
It is related with the shadow process that is waiting for a message to arrive from the client process.
It seems no db links involved there.. Just an OBJ$ query.

Yes..  What is the client? A monitoring tool or something? What does it do with the obj$.. Check the client and understand why it is waiting.. (another transaction, some input from somewhere and so on..)

That is related with the client is waiting for input.. That 's time in the client process itself ,
That 's also the time in the network between the client and the server. SQL*Net trace (with TIMESTAMPS) can be helpful to check the network between the client and server.