David, Have you considered that the bottleneck may not be in the database, but somewhere else? Is it possible that the delay is in the app/web server? Network problems? Why are you convinced that it is in the database? Tom -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of David Turner Sent: Thursday, May 26, 2005 2:53 PM To: oracle-l@xxxxxxxxxxxxx Subject: Interesting problem 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.=20 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 =09 __________________________________=20 Do you Yahoo!?=20 Yahoo! Small Business - Try our new Resources site http://smallbusiness.yahoo.com/resources/ -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l