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 file
on C: (local machine) which raises the question if the machine had enough
space on that drive and how fragmented it was... Oh, users....
Best regards to everyone,
Sergey


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


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




 

                    "Babich ,

                    Sergey"               To:     Multiple recipients of
list ORACLE-L <[EMAIL PROTECTED]>        
                    <SBabich@hande        cc:

                    xmail.com>            Subject:     Problem running a
report                                      
                    Sent by:

                    [EMAIL PROTECTED]

                    om

 

 

                    February 26,

                    2002 02:18 PM

                    Please respond

                    to 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: 
  INET: [EMAIL PROTECTED]

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: [EMAIL PROTECTED] (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).
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Babich , Sergey
  INET: [EMAIL PROTECTED]

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: [EMAIL PROTECTED] (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).

Reply via email to