PI57327: MISSING SESSION ATTRIBUTES WITH ORACLE 12 AS DATABASE SESSION PERSISTENCE WHEN MULTI-ROW CONFIGURATION IS ENABLED

8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• Missing session attributes with Oracle 12 as database session
  persistence when multi-row configuration is enabled
  
  WebSphere Application Server V 8.5
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server V 8.5.5    *
  *                  users using multi-row schema configuration  *
  *                  for database session persistence on Oracle  *
  *                  Database 12.                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: The session manager may fail to use     *
  *                      the Oracle Database 12  for session     *
  *                      persistence when using a multi-row      *
  *                      configuration.                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When using a multi-row configuration on Oracle Database 12,
  the session manager may not store all the affected attributes.
  This is because previous Oracle jdbc driver returns
  SUCCESS_NO_INFO which is different than other JDBC drivers.
  

Problem conclusion

• Changes were made to the session manager code to account for
  the behaviors on all versions of the Oracle JDBC drivers.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.10.  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:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP