RE: Problem running a report

[Babich , Sergey]

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 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----- From: Babich , Sergey [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 26, 2002 2:18 PM To: Multiple recipients of list ORACLE-L Subject: Problem running a report 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