PM27191: SETTING currentSchema CUSTOM PROPERTY ON DB2 JDBC DRIVER MAY CAUSE SQL EXCEPTIONS ON STARTUP

7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
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: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• A createTable exception may occur if one of the following is
  true.
  
  1. When the currentSchema custom property is set on the DB2
  JDBC driver and its value does not match the user id configured
  for session persistence.
  
  2. The SESSIONS table is created manually as a different user
  than the one configured for session persistence.
  
  DatabaseHashMap createTable Exception is:
  com.ibm.db2.jcc.am.SqlSyntaxErrorException: The name of the
  object to be created is
  identical to the existing name "DBUSER.SESSIONS" of type "TABLE"
  SQLCODE=-601, SQLSTATE=42710, DRIVER=3.59.81
  at com.ibm.db2.jcc.am.dd.a(dd.java:676)
  at com.ibm.db2.jcc.am.dd.a(dd.java:60)
  at com.ibm.db2.jcc.am.dd.a(dd.java:127)
  at com.ibm.db2.jcc.am.bn.c(bn.java:2546)
  at com.ibm.db2.jcc.am.bn.d(bn.java:2534)
  at com.ibm.db2.jcc.am.bn.b(bn.java:1966)
  at com.ibm.db2.jcc.t4.cb.h(cb.java:221)
  at com.ibm.db2.jcc.t4.cb.b(cb.java:47)
  at com.ibm.db2.jcc.t4.q.b(q.java:38)
  at com.ibm.db2.jcc.t4.rb.h(rb.java:114)
  at com.ibm.db2.jcc.am.bn.fb(bn.java:1961)
  at com.ibm.db2.jcc.am.bn.a(bn.java:3033)
  at com.ibm.db2.jcc.am.bn.c(bn.java:704)
  at com.ibm.db2.jcc.am.bn.executeUpdate(bn.java:688)
  at
  com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.pmiExecuteUpdate(WSJdb
  cStatement.java:1693
  at
  com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.executeUpdate(WSJdbcSt
  atement.java:1041)
  at
  com.ibm.ws.session.store.db.DatabaseHashMap.createTable(Database
  HashMap.java:541)
  at
  com.ibm.ws.session.store.db.DatabaseHashMap.initDBSettings(Datab
  aseHashMap.java:416)
  

Local fix

• This problem will not occur if WebSphere Application Server
  creates the SESSIONS table.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server users who  *
  *                  use session database persistence with DB2.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: If the custom property "currentSchema"  *
  *                      is set in the DB2 JDBC driver, an SQL   *
  *                      exception may be logged during          *
  *                      subsequent starts.                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the "currentSchema" custom property is set in the DB2
  JDBC driver, the sessions table is created with the value of
  the "currentSchema" custom property as the qualifier.  On
  subsequent server or application starts, an SQL exception may
  be logged because the Session Manager does not detect the
  previously created sessions table.
  

Problem conclusion

• A new Session Manager custom property "UsingCustomSchemaName"
  was introduced to properly detect a previously created
  sessions table.
  The fix will be integrated into fix packs 7.0.0.17 and
  6.1.0.39, and delivered as an interim Fix by request for
  v6.0.2.
  Please refer to the Recommended Updates page for fix pack
  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:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

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

• R700 PSY

     UP