Poor Performance With Query Called From JDBC Using Bind Variables Compared To A DATE Column
(Doc ID 1557194.1)
Last updated on MARCH 03, 2022
Applies to:
JDBC - Version 9.2.0.1 and laterOracle Database - Enterprise Edition - Version 9.2.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.
Symptoms
- A query called from JDBC uses bind variables bound with the setTimestamp method. These bind variables are compared to a column with type DATE.
- The plan for the query performs poorly, and may be found to be unstable.
- Desired index on the DATE column is not being used or that the predicate comparing the bind to the column is applied as a filter predicate rather than an access predicate when accessing the index, resulting in slower performance.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
Fix |
Workarounds |
References |