; 'Tim Gorman'
Sent: Wednesday, August 21, 2002 11:59
AM
Subject: RE: how to reduce SQL*Net more
data to client wait event
Tim, more specifically could large SQL
have been passed across
the
net ? Stored procedures could help here.
FWIW.
Mike
thank
you.
mike
-Original Message-From: Anjo Kolk
[mailto:[EMAIL PROTECTED]]Sent: Wednesday, August 21, 2002 1:09
PMTo: Multiple recipients of list ORACLE-LSubject: Re:
how to reduce SQL*Net more data to client wait event
No,
this is "to client", so
ing it to the server. Parse once/execute many
Anjo.
- Original Message -
From:
Johnson, Michael
To: Multiple recipients of list ORACLE-L
Sent: Wednesday, August 21, 2002 9:10
PM
Subject: RE: how to reduce SQL*Net more
data to client wait event
Tim, mor
: Re:
how to reduce SQL*Net more data to client wait event
Depending on the application, couldn't
these large pauses be performance problems in the client
program? Not a server tuning issue nor a SQL*Net tuning issue at
all? For example, if the client program was pausing a long
Monday, August 19, 2002 8:08 PM
> Subject: how to reduce SQL*Net more data to client wait event
>
>
> Hi,
>
>
>
> I am tuning a system at a client site and notice lots of waits for
> SQL*Net <http://213.46.46.10/cgi-bin/yappweb206#SQL*Net more data to
> client#SQL*
? Or would
that just be accounted for under "SQL*Net message from client"
events?
- Original Message -
From:
Suhen Pather
To: Multiple recipients of list ORACLE-L
Sent: Monday, August 19, 2002 8:08
PM
Subject: how to reduce SQL*Net more data
to cl
The BEQ (or BEQueath) protocol adapter is only usable within the server, not
outside and is actually the best to use when you can. TCP/IP is the most often
used protocol outside of a server and in a client/server configuration. Setting
TDU and SDU to something other than 2K (the default) can in
John,
That event can happen for a couple of reasons, but the most common one is that
the serverside has returned an error for the client side for an operation.
The client side isn't really expecting it so the server sends a break/reset
to the client. That gives the client a change to resync.
Anjo,
On a related topic: I always wanted to know what the 'SQL*Net break/reset to
client' (or to dblink) means... There isn't much out there :(
John Kanagaraj
-Original Message-
Sent: Tuesday, August 20, 2002 2:13 AM
To: Multiple recipients of list ORACLE-L
SQL*Net ships data (in
ORACLE-L
Sent: Tuesday, August 20, 2002 4:08
AM
Subject: how to reduce SQL*Net more data
to client wait event
Hi,
I am tuning a system at a client
site and notice lots of waits for SQL*Net
more data to client (97%) for a fraction
of the CPU consumed by the system
Suhen,
I can't see the report your link is pointing at, but I guess that the "more-data-to-client"
event is a big part of total waittime.
Basically the event indicates, that the server is trying to send data to
the client for a second, third time. Meaning that the it is sending consecutive
Hi,
I am tuning a system at a client site and notice lots of
waits for SQL*Net
more data to client (97%) for a fraction
of the CPU consumed by the system.
I know this is not to be characterized as an idle wait event
and can yield better performance if we increase
the packet size.
12 matches
Mail list logo
