PK49506: ISSUE WITH OPTIMISTIC CONCURRENCY CONTROL WITH JDBC MEDIATOR RELATED TO HANDLING THE OCC COLUMN

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
PK49506; 6.1.0.9: Issue with optimistic concurrency control with JDBC Mediator

APAR status

• Closed as program error.

Error description

• With a number of tables where the OCC column is nullable, not
  able to update the schema and add a 'not nullable' restriction
  since this is not a backward compatible change.
  
  Need the mediator to handle the update of the OCC column value
  in the following way:
  
  - if the value of the OCC column is null set it to 1. The
  'where' clause should check if the value IS NULL
  
  - else if the value of the column is not null, set it to current
  value + 1. The 'where' clause should check the the value is the
  same as the current value
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the JDBC Mediator in IBM WebSphere  *
  *                 Application Server version 6.0.2 and 6.1     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Problem with null columns and           *
  *                      concurrency control                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a database column used for optimistic concurrency control
  in the JDBC Mediator initially contains a null value,
  concurrency control will not work as expected.
  

Problem conclusion

• The JDBC Mediator will now take into account null values in
  concurrency control columns. Note that the best practice is to
  use non-nullable columns for optimistic concurrency control.
  However, in cases where this is not possible, the mediator
  will now behave correctly.
  The fix for this APAR is currently targeted for inclusion
  in fixpack 6.1.0.13.
  Please refer to the recommended updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• JDBC     MEDIATOR
  

Fix information

• Fixed component name

  WEBSPH APP SERV

• Fixed component ID

  5724J0800

Applicable component levels

• R60A PSY

     UP

• R60H PSY

     UP

• R60I PSY

     UP

• R60P PSY

     UP

• R60S PSY

     UP

• R60W PSY

     UP

• R60Z PSY

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP