JDBC driver and poor SQL execution plan

Follow-up to performance impact of java.sql.TimeStamp from Oracle/Java/Others

I was asked to create a index for a simple query. it is using FULL table scan. The index works find on test server.
On live server, it refuse to use the index.
I checked the table stats, it is up-to-date.
I manually execute the query, it was using the index.

When we configured our test app server using the live data, , it used the index correctly.
When the driver used in live server was copied to test server, the query run very slow.

No doubt the JDBC driver cause problem again.

Hongfeng Sun : 10 Dec 2008 17:34 |  Tags: Oracle-Tune |  Comments (0) |  Trackbacks (1) |  Report a problem