While working on application performance issues, I noticed significant discrepancy in time reported by SQL Trace and actual time taken by the application. Total Elapsed time reported by SQL Trace was 180 seconds, but it took 500 seconds to run it. (It was a PL/SQL procedure. I just measured the time to run the PL/SQL procedure.) Parse Elapsed Time reported by SQL Trace is 90 seconds, but V$SESSTAT reported parse time elapsed of only 15 seconds. Parse CPU Time reported by SQL Trace is 60 seconds, but V$SESSTAT reported parse time CPU of only 14 seconds. Any explanations on why such a big discrepancy on reported time? Thanks in advance, Jay **************************************************************************** This electronic message contains information from CTIS, Inc., which may be company sensitive, proprietary, privileged or otherwise protected from disclosure. The information is intended to be used solely by the recipients named above. If you are not an intended recipient, be aware that any review, disclosure, copying, distribution or use of this transmission or its contents is prohibited. If you have received this transmission in error, please notify us immediately at [EMAIL PROTECTED] **************************************************************************** -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Jay Mehta INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
