Oracle Point, Oracle Life.

With introduction of Oracle Application Server, the previous oralce application, mainly oracle forms and reports, is required to immigrate to web platform. That means, Oracle JDBC, impletementing through OC4J, plays more important role in the onward application.
An problem recently experienced is that a long-writting procedure with DML statement could not be submitted without explicit commit statement. The solution for this kind of problem is always to add explicit commit definitely.

Investgating this issue, some points are listed for note.

1. Autocommit option is default in oracle JDBC
2. Autocommit option is required to be disabled if the select
   statement follows by FOR UPDATE; Otherwise, an error ora-01002:
   fetch out of sequence will arise.
3. By default, the DML statement in connection with Oracle JDBC will
   be committed right after the successful execution.
4. In order to improve the performance, especially on the long
   transaction, the autocommit option is disabled and smart commit
   strategy or batch executing is required.
5. As autocommit is disabled, explicit or implict commit for batch
   executing will be placed carefully.

An useful article is listed as http://www.javaperformancetuning.com/tips/jdbctransaction.shtml for “JDBC transaction performance”.

Popularity: 2% [?]

Recently, I was using an useful script to do database healthcheck and found it’s very helpful. This script was originally from Oracle Metalink (Doc Id: 1019592.6) and it not only diagnoses some potential problems of database, but offers some suggestion to amend database.

That’s a real good one to clarify some internal concepts of oracle database. Highly Recommended!!!

Also available at: http://www.oraclepoint.com/topic.php?filename=103&extra=page%3D1

Popularity: 3% [?]