PK77100: LOB DATA NOT STORED IN SESSION TABLE IN SOME INSTANCES WHEN USING SESSION PERSISTENCE TO DB2

Fixes are available

APAR status

Closed as program error.

Error description

When fullyMaterializeLobData is set to false in the JDBC driver
custom properties for the DB2 driver being used, the session
persistence code fails to write LOB's to the session table.  The
data is instead stored in memory and thus can be lost when the
server is recycled.

Local fix

Keep fullyMaterializeLobData set to true in the driver custom
properties settings.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V6.0.1 for z/OS                             *
****************************************************************
* PROBLEM DESCRIPTION: Session Manager does not return an      *
*                      existing session attributes             *
*                      persisting in session persistence in a  *
*                      failover application.                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a failover application retrieves
an existing session attributes
persisting into the lob data type
column defined in the session
persistence table, session attributes
will not be retrieved since the lob
data is not fully materialized
properly.

Problem conclusion

The session manager data retrieval mechanism is enhanced to
fully materialize the data from the database in the
configuration of datasource property fullyMaterializeLobData
disabled.

APAR PK77100 is currently targeted for inclusion in Service
Level (Fix Pack) 6.0.2.35 of WebSphere Application Server V6.0.1
for z/OS.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PK77100
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
601
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-12-08
Closed date
2009-03-31
Last modified date
2009-06-30

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

PK86983 PK90248

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R601 PSY UK46540
UP09/05/30 P F905

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK77100: LOB DATA NOT STORED IN SESSION TABLE IN SOME INSTANCES WHEN USING SESSION PERSISTENCE TO DB2

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R601 PSY UK46540

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

Document Information

Share your feedback

Need support?