[Date Prev][Date Next][Thread Prev][Thread Next]
[Author Index]
[Date Index]
[Thread Index]
[SQR-USERS Info]
[SQRUG Home Page]
Re: [sqr-users] How SQR program is connection to the database-- clarification
George,
I got your point. But if all other conditions are the same, program is the
same, should I see different in time when protocol is changed form TCP to
BEQ? My DBA thinks it should, because program is connecting locally
instead of going over the network, but I don't see a difference. Program
runs for 2.5 hours, when I run traces - in tkprof I can account for 60 min
(and I don't know where the rest of the time is going), event 10046 gives
me 40% time in "SQL*Net message to client". I'll try to re-write this
program to minimize number of calls issued to Oracle, but we have some
program we cannot re-write (PeopleSoft), that's why I was wondering if I'm
missing some parameters or configuration.
Thanks,
Yelena Kontorovich
Technical Consultant
847.948.2927
yelena_kontorovich@baxter.com
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, re-transmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the content.
"George Jansen"
<GJANSEN@aflcio To: sqr-users@sqrug.org
.org> cc:
Sent by: Subject: Re: [sqr-users] How SQR
program is connection to the
sqr-users-admin database-- clarification
@sqrug.org
12/18/2003
07:29 AM
Please respond
to sqr-users
Yelena,
You're welcome. Sorry I wasn't clear; to elaborate
1. My point is that "SQL*Net message to client" is not necessarily a
useful measure. My tiny script allows you to run that wait event
arbitrarily high, whether you are connected through BEQ or over a
network. Same system, same time of day, yet the wait time increases
directly with the sleep interval between fetches. (See below.)
2. The two runs you quote vary only because one connected via MTS,
which throws my quick-and-dirty accounting off.
3. I don't know about complex calculations, because I don't know what
your SQR is doing. Is it a standard PeopleSoft SQR? If so, which? In
either case, do you know, within your SQR, where the time is going?
George Jansen
P.S. One more screen shot:
/tmp>sqr snooze.sqr scott/tigress 1
SQR V4.3.2.2
Copyright (C) SQRIBE Technologies, 1994-98. All Worldwide Rights
Reserved.
SQL*Net message from client -> 521
SQL*Net message to client -> 0
SQR: End of Run.
/tmp>sqr snooze.sqr scott/tigress 10
SQR V4.3.2.2
Copyright (C) SQRIBE Technologies, 1994-98. All Worldwide Rights
Reserved.
SQL*Net message from client -> 5015
SQL*Net message to client -> 0
SQR: End of Run.
/tmp>sqr snooze.sqr scott/tigress 100
SQR V4.3.2.2
Copyright (C) SQRIBE Technologies, 1994-98. All Worldwide Rights
Reserved.
SQL*Net message from client -> 50015
SQL*Net message to client -> 0
_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users
_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users