PQ78128: Adminserver will not start due to ORACLE DB Locks not released.

APAR status
Closed as duplicate of another APAR.

Error description
There is a tiny window in which the admin database has to
be -between- making an update and closing the statement.
At that exact moment, the database must go down completely
causing a locking problem.  This can occur even with the
latest CM code. This is why it's not a very big window,
and why we've never seen the problem before.
Local fix
Workaround: You simply have to force the sessions closed in
Oracle, this will cause the locks to be released and the server
to restart.
Problem summary Problem conclusion Temporary fix Comments
This is a duplicate of 
PQ78605.
APAR information
APAR number PQ78128
Reported component name WEBSPHERE AE SO
Reported component ID 5630A2202
Reported release 400
Status CLOSED DUA
PE NoPE
HIPER NoHIPER
Submitted date 2003-09-04
Closed date 2004-07-06
Last modified date 2004-07-06

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Applicable component levels


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ78128
IBM Group: Software Group
Modified date: Jul 6, 2004