You can use wait events too, Oracle wait interface a practical guide to performance diagnostics tuning from richmond shee has a good example Juan Carlos Reyes Pacheco OCP -------Original Message------- From: ryan_gaffuri@xxxxxxxxxxx Date: 10/28/04 11:50:11 To: cspabba@xxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx Cc: Chandra Pabba Subject: Re: How to calculate the CPU Time for a procedure dbms_profiler should help with your requirement. you may not be able to get the kind of granularity you want unless you fire the procedures one at a time and look at trace files. this sounds like something coming down from management.... 95% of performance problems with stored code is either due to 1. bad query 2. running a query 100,000 times when it should be run once. you can probably use dbms_profiler to figure out was is taking the longest and tune from there. -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l