Interesting problem
- From: David Turner <dnt9000@xxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Thu, 26 May 2005 11:52:40 -0700 (PDT)
We've been using set client info on many of our
production systems for some time and this helps us
create resource usage reports so we can identify
owners of bottlenecks. However, we do have some older
systems where this isn't implemented and the
transactions are much shorted so it's very hard to
identify why some of our sessions have longer response
times.
For instance I have a query that scans maybe 4 blocks
and returns data instantly when I run it manually but
throughout the day periodically it takes well over 10
seconds, which isn't acceptable.
I've set up a script that montors the db every minute
but it just doesn't appear to be catching what is
causing our normally fast running queries to
periodically run long. If any of you have any
suggestions on diagnosing this I'd appreciate it.
The main areas I've focused on are
A minute by minute report of v$session and v$process
info
Many of the standard performance tuning stats tracked
via statspack
Cronjobs
Feed processes
with no luck so far.
Thx, Dave
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new Resources site
http://smallbusiness.yahoo.com/resources/
--
http://www.freelists.org/webpage/oracle-l
- Follow-Ups:
- Re: Interesting problem
- From: Stephane Faroult
- Re: Interesting problem
- From: dbvision
Other related posts:
- Re: Interesting problem
- From: Stephane Faroult
- Re: Interesting problem
- From: dbvision