Pings can be misleading.
There's 7 layers to the OSI model.
Ping only reaches the third layer, the Network layer.
The Transport layer is not tested by a ping.
Ping will tell you that your network is up, but it tells
you nothing about the state of the server. It's possible
( and happens
For what it's worth, we had the same thing going on here recently and have
not resolved it. In our case, it is a visual basic app running what is
essentially a batch job (don't ask me why a batch job was written as a VB
app; I just work here). The client is a PC, and the database is on Tru64
Funny you should mention sunspots since that's what some of our people
are saying along with the phase of the moon. When we find a solution
(this is business critical, failure is not an option), I'll post a
summary.
Thanks to all for the suggestions.
Stephen
[EMAIL PROTECTED] 10/30/02 08:14AM
This sounds like a possible queueing (i.e., load-induced) issue.
Queueing issues show up as application works fine sometimes, but really
slow other times. The impetus for the really slow behavior is when you
increase concurrent load on the resource in question (here, the net)
just enough that
PROTECTED]
cc:
Subject:RE: SQL*Net Message to client/SQL*Net more data to client
This sounds like a possible queueing (i.e., load-induced) issue.
Queueing issues show up as application works fine sometimes, but really
slow other times. The impetus for the really slow
on that hockey-stick-shaped performance curve. (Sorry I can't show
pictures here in text; they'll all be in the book due out in about
June.)
I'd like to place my order now please :)
--- Cary Millsap [EMAIL PROTECTED] wrote:
This sounds like a possible queueing (i.e., load-induced) issue.
This is called Blame Storming. Every component works fine but
response time sucks and the problem is some other area. So how do we
turn Blame Storming into Brain Storming?
Check out the network components. One of the problems is that the
network people look at utilization, instead of response
Stephen,
Sounds like you've already done plenty of hunting. Do you know what these
waits were like previously?
Perhaps someone can correct me if I'm mistaken but does a listener not
responding error indicate the problem is getting to the server in general,
not the instance itself. Perhaps
Anjo,
They have reported the results of ping times and said that response
times are within spec. They have told me that the network card is
handling x bytes per second without errors and that the card is
capable of many times that throughput. They have swtiched network cards
8 times last week
Stephen
Can they tell you what the ping times were before? Some applications
are more sensitive to slower networks than others, probably because they
make more network round trips. Even if the ping times are within spec, if
they have increased, that might cause an issue. Just a thought for
10 matches
Mail list logo
