RE: Problem running a report

From: Babich , Sergey <SBabich_at_handexmail.com>
Date: Tue, 26 Feb 2002 11:53:32 -0800
Message-ID: <F001.00418F68.20020226115332@fatcity.com>

Thank you, Mladen. It's always good to know that the guess was right  

-----Original Message-----
Sent: Tuesday, February 26, 2002 2:38 PM To: Multiple recipients of list ORACLE-L  

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.

-----Original Message-----
Sent: Tuesday, February 26, 2002 2:18 PM To: Multiple recipients of list ORACLE-L

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 office (WAN) it gets stuck and takes a few hours if it completes at all. Here is the output from V$SESSION_WAIT for the session:

  SID       SEQ#  EVENT                      P1TEXT             P1  P1RAW
P2TEXT             P2  P2RAW     P3TEXT             P3  P3RAW     WAIT_TIME

SEC_WT STATE

• --------- ------------------------- ---------- --------- -------- ---------- --------- -------- ---------- --------- -------- --------- ------ ---------

   82      31384  SQL*Net message from clie  driver id   675562835  28444553


#bytes              1  00000001                      0  00                0

0 WAITING After some time:  

  SID       SEQ#  EVENT                      P1TEXT             P1  P1RAW
P2TEXT             P2  P2RAW     P3TEXT             P3  P3RAW     WAIT_TIME

SEC_WT STATE

• --------- ------------------------- ---------- --------- -------- ---------- --------- -------- ---------- --------- -------- --------- ------ --------

   82      33799  SQL*Net message from clie  driver id   675562835  28444553


#bytes              1  00000001                      0  00                0

0 WAITING   and so on.(SEQ# increases and then resets).  

At the headquarters (LAN) it shows the same event after scattered read and it is done. Could that be a SQL*Net issue between LAN and WAN?

Any ideas are appreciated as always.

TIA, Sergey    

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Babich , Sergey
  INET: SBabich_at_handexmail.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Received on Tue Feb 26 2002 - 13:53:32 CST