JDBC performance problems of setTimestamp

by:dbanotes@gmail.com(Fenng)

Author:Fenngpublished in thedbanotes.net.

accidental discovery three years ago of a technical issue. At that time, compared hurry, to avoid that is passed out. Metalink has actually now on this issue addressed as a Bug.

Description of the problem: through JDBC query of the Java application, SQL performance anomalies. Table field used DATA type, against the regional field time for a very small range (should be expected to take INDEX RANGE SCAN), in SQL Map specified on the index, found invalid. Is still FULL TABLE SCAN.

culprit: setTimestamp () for the value of bundled TIMESTAMP type, and this type of comparison of DATA, CBO will choose full-table scan.

Trace can be observed through the abnormal behavior. TIMESTAMP in Oracle's JDBC 9.2.0.1, there will be a continuous several versions in fact have a similar problem.

solution: using setString () rather than setTimestamp () method.

this story tells us, JDBC fact, the problem Tingduo. Similarly, TIMESTAMP lot of potential problems.

- EOF -

articles | Related Articles

• Oracle-L Steve Adams to a change in Chushan



• Oracle DBMS_SUPPORT HOW-to



• write the history of Oracle - ORACLE company Legend



• write the history of Oracle - ORACLE company Legend (2)

comment on the number (0) |Add Comments

this Web site:http://www.dbanotes.net/database/jdbc_settimestamp_performance.html

The author also said that the last of what? FollowTwitter/Fenng

DBA notes concept: the most simple technology to achieve maximum benefits!

original link:http://www.dbanotes.net/database/jdbc_settimestamp_performance.html