PQ66035: FOR EVERY START OF WEBSPHERE THERE IS AN ADDITIONAL ENTRY IN EJSADMIN.LOCK_TABLE TABLE AND ADMIN DB2 IS ON OS/390 REMOTELY.

 Fixes are available

4.0.5: WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)
System Management Component Cumulative Fix for 4.0.2/4.0.3/4.0.4 /4.0.5



APAR status
Closed as program error.

Error description
Problem: Customer is having a WAS4.0 1 AE on AIX and Admin
repository is on DB2 with OS/390 remotely.
When ever customer restarts WAS , they see that there is an
additional entry in repository  EJSADMIN.LOCK_TABLE table.
.
Cause :
It seems the DDL for the admin repository for DB2/390 is called
db2390.sql in the bin directory in the WebSphere install.  As it
turns out, the DDL is missing the primary key clause on
the definition for the LOCK_TABLE.                             n
Addnl error: Another customer noted the unique index for the
EJSADMIN.LOCK_TABLE is missing. Here is the missing entry:
CREATE TYPE 2 UNIQUE INDEX EJSADMIN.LCK_IX ON
       EJSADMIN.LOCK_TABLE
       ( NAME );
Local fix
WorkAround : There is no work around.
Problem summary
****************************************************************
* USERS AFFECTED: For WebSphere Application Server 4.0 users   *
*                 having DB2 installed on a 390 system         *
****************************************************************
* PROBLEM DESCRIPTION: For every start of WebSphere there is   *
*                      an additional entry in                  *
*                      EJSADMIN.LOCK_TABLE                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The DDL for the admin repository for DB2/390 is called
db2390.sql in the bin directory. As it turns out, the DDL is
missing the primary key clause on the definition for the
LOCK_TABLE.  Another error: the unique index for LOCK_TABLE is
missing too.
Problem conclusion
The new ddl (db2390.sql) has added primary key on LOCK_TABLE
to avoid additional entry existing in LOCK_TABLE. The new ddl
has also created UNIQUE INDEX on LOCK_TABLE to resolve UNIQUE
INDEX missing problem.
Temporary fix
Have posted the efix on the wasdoc0\apars\PQ66035.  Wait for res
ponse.
Comments
APAR information
APAR number PQ66035
Reported component name WEBSPHERE AES A
Reported component ID 5630A2300
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-09-10
Closed date 2002-10-17
Last modified date 2002-10-17

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
ADMINSVR          

SRLS

Fix information
Fixed component name WEBSPHERE AES A
Fixed component ID 5630A2300

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ66035
IBM Group: Software Group
Modified date: Oct 17, 2002