Hey, good point! When we had some ODBC performance problems a few years ago, I attempted to turn on ODBC tracing but it was already on. Turned it off and deleted the 100s of MB of ODBC trace and all was well. :) Rich Rich Jesse System/Database Administrator rich.jesse@xxxxxxxxxxxx Quad/Tech International, Sussex, WI USA -----Original Message----- From: DENNIS WILLIAMS [mailto:DWILLIAMS@xxxxxxxxxxxxx] Sent: Thursday, February 05, 2004 9:12 AM To: 'oracle-l@xxxxxxxxxxxxx' Subject: RE: Slow ODBC connectivity Patrice Since it sounds like an in-house application, you might have the developers insert a statement to turn tracing on. Review of the trace might give you an idea of where the delays occur. From your posting, it sounds like you are assuming ODBC is the culprit, yet you also mention that you found one SQL statement that is causing significant delay itself. The question is whether the delay is due to ODBC or due to the SQL statements. Sometimes problems occur just due to the amount of network traffic back and forth between the server and the client. I think this question must be resolved before you decide on a tuning plan. A detailed trace should reveal the answer to this question. As Cary Millsap says in his book, this may be a situation where the SQL wait times are significant and can't be treated as inconsequential. Good luck, these types of situations can require a lot of time and patience to unravel. Dennis Williams ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------