PQ78528: LONG SERVER RECYCLE TIMES USING DB2 SESSION PERSISTENCE V2 AND A UNIQUE INDEX OF ID AND PROPID. | |||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
APAR status Closed as documentation error. Error description When recycling the WebSphere 401 system, and using DB2 Session Persistence V2 with a unique index of ID and PROPID that is described in the assembling j2ee applications manual SA22-7836-05. Chapter 8, under the section configuring websphere for z/OS to maintain session data in a DB2 database instead of in-memory. A unique index must be created using ID and PROPID, if only these two columns are used the problem occurs. The example shows using ID,PROPID and APPNAME which is correct.Local fix add APPNAME to the columns of the unique index.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: Server V4.0.1 for z/OS: Assembling J2EE * * Applications," SA22-7836-06, does not * * include APPNAME as one of the table * * columns for which the DB2 Administrator * * must create a type 2 unique index. * **************************************************************** * RECOMMENDATION: * **************************************************************** The section "Configuring WebSphere for z/OS to maintain session data in a DB2 database instead of in-memory" contained in Chapter 8 of "WebSphere Application Server V4.0.1 for z/OS: Assembling J2EE Applications," SA22-7836-06, needs to be updated to indicate that APPNAME as one of the table columns for which the DB2 Administrator must create a type 2 unique index.Problem conclusion The following paragraph and example contained in Chapter 8, section "Configuring WebSphere for z/OS to maintain session data in a DB2 database instead of in-memory," of "WebSphere Application Server V4.0.1 for z/OS: Assembling J2EE Applications," SA22-7836-06: The DB2 Administrator must also create a type 2 unique index on the ID and PROPID columns of this table. The following is an example of the index definition: CREATE TYPE 2 UNIQUE INDEX <database_name>.<index_name> ON <database_name>.<table_name> (ID, PROPID) USING STOGROUP <group_name> ERASE NO BUFFERPOOL BP0 CLOSE YES; Will be changed to the following: The DB2 Administrator must also create a type 2 unique index on the ID, PROPID, and APPNAME columns of this table. Following is an example of the index definition: CREATE TYPE 2 UNIQUE INDEX <database_name>.<index_name> ON <database_name>.<table_name> (ID, PROPID, APPNAME) USING STOGROUP <group_name> ERASE NO BUFFERPOOL BP0 CLOSE YES; This paragraph and example is included in the description of how to set up DB2 Session Persistence Version 1, and the description of how to set up DB2 Session Persistence Version 2. NOTE: Periodically, we refresh the documentation on our Web site, so these changes might have been made before you read this text. To access the latest on-line documentation, go to the product library page at: http://www.ibm.com/software/webservers/appserv /zos_os390/library/Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ78528
IBM Group: Software Group
Modified date: Oct 23, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.