Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Slow ODBC connectivity
Another place to look at is ODBC DataSource parameter called "Preftch
Count". By default it is set to 10, which means for the query
retrieving 1000 rows ODBC will make 100 trips to the database. Don't be
afraid to increase this parameter in DataSource configuration (I have it
set to 1000).
Igor Neyman, OCP DBA
ineyman_at_perceptron.com
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Jesse, Rich
Sent: Thursday, February 05, 2004 10:32 AM
To: 'oracle-l_at_freelists.org'
Subject: RE: Slow ODBC connectivity
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_at_qtiworld.com Quad/Tech International, Sussex, WIUSA
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
![]() |
![]() |