Oracle JDriver serializable problems

Question

I'm testing optimistic locking issues for a new application. The current
          prototypes are running with Oracle 8.1.7, WLS 6.1 SP1, NT 4.0. However
          I'm seeing different behaviour when using the Weblogic JDriver and the
          Oracle thin driver.
          I've create a stateless session bean to wrap an entity bean. Both beans
          are managed by CMT, the session uses Required and the entity Mandatory.
          The session bean method performing the update is configured with
          TRANSACTION_SERIALIZABLE.
          When executed with two clients using the Weblogic
          JDriver(weblogic.jdbc.oci.Driver) I can make two calls (which increases my
          connection pool size to 2)each one is rejected and works as expected.
          However the next and remaining attempts refuse to generate the ORA-8177.
          If I restart the WLS server it produces exactly the same results. I've
          tried configuring the driver with bin/oci816_8 and bin/oci817_8 paths when
          starting weblogic.
          I then tried with the Oracle thin driver (oracle.jdbc.driver.OracleDriver)
          and this appears to work fine.
          Has anyone seen this behaviour ? Could this be a problem with the JDriver
          or Oracle's OCI ?
          Darren
          

Answer 1

We had similar performance issues in our environment, once we upgraded from 9.2.0.2 to 10.2.0.2.
Oracle: 10.2.0.2
SAP: 4.7x110
OS: SOLARIS 9 64bit
The above mentioned notes were very helpful. We had to install an oracle patch as well (found on marketplace)  --  6321245
and make the following oracle parameters changes:
pga_aggregate_target - 144MB (default = 25MB)
*.event="10027 trace name context forever, level 1"
*.event="10028 trace name context forever, level 1"
*.event="10162 trace name context forever, level 1"
*.event="10183 trace name context forever, level 1"
*.event="10191 trace name context forever, level 1"
*.event="10629 trace name context forever, level 32"
*.event="38068 trace name context forever, level 100"
*.event="38043 trace name context forever, level 1"
*.optimizer_index_caching=50
*.optimizer_index_cost_adj=20
*.parallel_execution_message_size=16384
*._b_tree_bitmap_plans=FALSE
*._index_join_enabled=FALSE
*._optim_peek_user_binds=FALSE
*._optimizer_mjc_enabled=FALSE
*._sort_elimination_cost_ratio=10
Remove
*.optimizer_features_enable='9.2.0'
HTH