Subject: RE: Pr
Thanks to everyone who responded. The database is centralized. Yesterday I
PINGed some machines in different offices (and TRACERTed, too) right from
the server, and the response time was under 100 msec. However, some offices
reported it to have run normally. That particular report creates a big fi
Thank you, Mladen. It's always good
to know that the guess was right
-Original Message-
From: Gogala, Mladen
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 26, 2002
2:38 PM
To: Multiple recipients of list
ORACLE-L
Subject: RE: Problem running a
report
That wa
Look at v$session_event for session 82. That will tell the story .
Anjo.
"Babich , Sergey" wrote:
Hi,
ladies and gentlemen,
Here
is a good one. We have 25 offices nation wide, running similar reports.
At the headquarters the one in consideration takes 12 min to complete.
Any other off
Are you using remote connections to a centralized database, or does each
office have its own database?
Tracert and netstat commands should help you figure out if its a network
issue.
Regards
Raj
That
wait is, essentially, an idle wait. That means that the database processes are
waiting for the
message from the client, which, quite obviously, is
taking it's time. Yes, I think that getting yourself
a
Snoopy (network engineer with a packet sniffer) would probably be a good
idea.
-
