PQ48625: ON DB2/390, ADMINSERVER FAILS TO START WHEN LOCK_TABLE IS CREATED


APAR

APAR status
Closed as program error.

Error description
The repository database is set up with the tables on DB2/390.
The dbInitialized flag with any option, there or not, does not
stop the attempt to create the LOCK_TABLE with a permission
error. The adminserver fails to start.
PQ46883 is the cm component.
Local fix
Problem summary
is required.
The cleaner (which also respect the boolean value of the Java
properties) implementation implies the following boolean
semantics for the properties:
com.ibm.ejs.sm.adminServer.dbInitialized
(also triggered by command line -dbInitialized)
.
1. When "true" means that the WAS repository was initialized.
   This will try to skip the creation of the tables. However,
   a check has been put in to also lookup the database
   metadata to ensure that the WAS repository tables
   are really there before skipping the table creation based
   on this property.  So for situations where the DBA wants to
   create his own tables, as in DB2 on S/390, this value should
   be set to true.
.
2. When "false" means that the WAS repository was not
   initialized.  Will try to create the WAS repository tables.
.
com.ibm.ejs.sm.adminServer.initializeDb
(also triggered by command line -initializeDb)
.
1. When "true" will onlu try to create the WAS repository and
   exit. No adminserver process or app server process will be
   left active. It's job is to create the repository tables ...
   that's it!!
.
2. When "false" ... will not do the exit as described in (1)
   and keep the adminserver process running.
.
These two properties in tandem create some dynamic
configurations for the adminserver startup.
semantics for the properties:com.ibm.ejs.sm.adminServer.dbInitialized(also triggered by command line -dbInitialized).1. When "true" means that the WAS repository was initialized.This will try to skip the creation of the tables. However,a check has been put in to also lookup the databasemetadata to ensure that the WAS repository tablesare really there before skipping the table creation basedon this property. So for situations where the DBA wants tocreate his own tables, as in DB2 on S/390, this value shouldbe set to true..2. When "false" means that the WAS repository was notinitialized. Will try to create the WAS repository tables..com.ibm.ejs.sm.adminServer.initializeDb(also triggered by command line -initializeDb).1. When "true" will onlu try to create the WAS repository andexit. No adminserver process or app server process will beleft active. It's job is to create the repository tables ...that's it!!.2. When "false" ... will not do the exit as described in (1)and keep the adminserver process running..These two properties in tandem create some dynamicconfigurations for the adminserver startup.
Problem conclusion
com/ibm/ejs/sm/server/ManagedServer.java
com/ibm/ejs/cm/lock/RowUpdateLock.java
com/ibm/ejs/cm/lock/TableLockLock.java
com/ibm/ejs/sm/server/AdminServer.java
com/ibm/ejs/cm/lock/RowUpdateLock.java
com/ibm/ejs/cm/lock/TableLockLock.java
com/ibm/ejs/cm/lock/RowUpdateLock.java
com/ibm/ejs/cm/lock/TableLockLock.java
Temporary fix
Comments
APAR information
APAR numberPQ48625
Reported component nameWAS ADVANCED SU
Reported component ID5648C8402
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2001-05-09
Closed date2001-05-17
Last modified date2002-02-04

APAR is sysrouted FROM one or more of the following:

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


Modules/Macros
JDBC
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS ADVANCED SU
Fixed component ID5648C8402

Applicable component levels
R300 PSYUP
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ48625
IBM Group: Software Group
Modified date: 2002-02-04