Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Database sloowww...trying to figure out why...

RE: Database sloowww...trying to figure out why...

From: Chris Stephens <>
Date: Tue, 30 Mar 2004 16:42:39 -0600
Message-ID: <>

Thanks! ...I know I should be tracing sessions that are important to the business but am hesitant to dive into the situation. I've read the theory part of cary's book...but stopped when I hit the chapter on walking through the trace files and haven't picked it back up. Look's like it's a great opportunity to dig in.  

...and thank you to whoever suggested ubtools.

...I had no idea that was available for free.

...I'll be studying cary's book for a while but in the meantime, I'm going
to press for permission to trace user sessions when they start complaining and running them through ubtools to see if I can't make sense of it as I learn.  

...I think I remember people saying that it is difficult to identify
particular sessions in an apps environment. ...can anyone confirm that?
...if not...I'm sure I'll find out for myself tomorrow!


-----Original Message-----
From: Mike Schmitt [] Sent: Tuesday, March 30, 2004 4:28 PM
Subject: RE: Database sloowww...trying to figure out why...  

As someone else mentioned, I think you might need to spend a little more time collecting the right data and then start fixing your problems by priority. I am guessing that all of your users are complaining about performance at this point.

Something that I have noticed in the past when working on Oracle apps installations is that poorly custom coded reports, jobs, and forms can really tear away at the performance as they slowly get introduced. You should be able to find out which jobs are the most critical and taking the longest to run within apps. Start tracing those jobs as they run and working on improving their performance. In other words, improving the puzzle piece by piece can often improve the whole.

Also, watch out for forms that allow the users to run selects without providing fields to select by. These can easily chew up a lot of resources.

Anyways, Im sure people on here will be able to give you better advice

Good luck : )

....much of the problem lies in custom scripting not in a particular

Please see the official ORACLE-L FAQ:

To unsubscribe send email to: put 'unsubscribe' in the subject line.
Archives are at
FAQ is at
Received on Tue Mar 30 2004 - 16:39:34 CST

Original text of this message