Re: Some indexes not used in JDBC call
- From: "kuassi.mensah@xxxxxxxxx" <kuassi.mensah@xxxxxxxxx>
- Date: 27 Feb 2007 09:28:00 -0800
Hi,
As i have explained in Oracle Forums, even though this is my own
speculation, if you were using JDBC-Thin then this is certainly due to
the fact that SQL*plus and JDBC are not using the same version of TTC
protocol messages. JDBC-Thin is pure Java and has to turn each release
of C/OCI based protocol into pure Java; sometimes the version being
used by a particular JDBC release is not in sync with the one used by
SQL*Plus. If you were using JDBC-OCI then the problem is elsewhere.
Kuassi http://db360.blogspot.com
On Feb 14, 7:27 am, samuelroll...@xxxxxxxxx wrote:
Hello everyone,
I'm having a problem where a JDBC PreparedStatement without bind
parameters can take more than a minute to execute a query that takes
less than a second to execute in SQL*Plus. The query is identical, the
database instance is the same, neither query is cached, and the query
returns only 18 records with 11 columns all of which are either
VARCHAR2 or NUMBER. I'm using Oracle's JDBC 2.0 drivers
(classes12.jar) and Oracle 8i (Release 8.1.7.4.0) database. Oracle DB
is set to use the cost-based optimizer.
I did an explain plan in SQL*Plus and via JDBC. It turns out that some
of the unique indexes that are used when executing the query in
SQL*Plus are not used when executing via JDBC.
Does anyone know why this would happen?
Thanks,
Sam
.
- References:
- Some indexes not used in JDBC call
- From: samuelrollins
- Some indexes not used in JDBC call
- Prev by Date: Aggregate function error with Access database
- Next by Date: Re: SQL that performs division
- Previous by thread: Re: Some indexes not used in JDBC call
- Next by thread: JAVA DEVELOPERS GC/CITIZENS
- Index(es):
Relevant Pages
|
