Some indexes not used in JDBC call
- From: samuelrollins@xxxxxxxxx
- Date: 14 Feb 2007 07:27:33 -0800
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
.
- Follow-Ups:
- Re: Some indexes not used in JDBC call
- From: kuassi.mensah@xxxxxxxxx
- Re: Some indexes not used in JDBC call
- From: Juha Laiho
- Re: Some indexes not used in JDBC call
- Prev by Date: Prepared Statement Joda Time
- Next by Date: Re: Prepared Statement Joda Time
- Previous by thread: Prepared Statement Joda Time
- Next by thread: Re: Some indexes not used in JDBC call
- Index(es):
Relevant Pages
|
|