Re: How to trace the root cause of "SQL*Net more data to client" for only few executions of a query
From: Mladen Gogala <gogala.mladen_at_gmail.com>
Date: Wed, 9 Oct 2019 15:57:46 -0400
Message-ID: <2183d6b1-e903-43d4-ce88-e1d1b4d9e513_at_gmail.com>
Date: Wed, 9 Oct 2019 15:57:46 -0400
Message-ID: <2183d6b1-e903-43d4-ce88-e1d1b4d9e513_at_gmail.com>
Well, kernel socket buffer may block if the network subsystem was not able to deliver the data. That is why increasing net.core.wmem_default and net.core.wmem_max are being checked during Oracle installation.
On 10/9/19 3:13 PM, kyle Hailey wrote:
> And yes, Tanel is the expert here, see SQL*Net message to client
> <http://blog.tanelpoder.com/2008/02/10/sqlnet-message-to-client-vs-sqlnet-more-data-to-client>
>
>
> "I”ll reiterate that both |SQL*Net message to client| and |SQL*Net
> more data to client| waits only record the time it took to write
> the return data from Oracle’s userland SDU buffer to OS
> kernel-land TCP socket buffer. "
>
-- Mladen Gogala Database Consultant Tel: (347) 321-1217 -- http://www.freelists.org/webpage/oracle-lReceived on Wed Oct 09 2019 - 21:57:46 CEST