PQ84692: Multiple Server startup caused deadlock in Naming Binding Table with DB/2 running on S/390. | |||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description Environment is multiple servers during startup using DB/2 on S/390 WebSphere is running on AIX with WSAS 4.05. Getting SQL0913N in DB2 log. Gets the following errors in system.out. [1/22/04 2:39:17:244 EST] dcdd628 ExceptionUtil X CNTR0021E: Non-application exception occurred on bean BeanId(admin#nssrcm.jar#Binding, BindingKey(MTASProvisioningQueryHome,711a30-00f6-e5bc-9b3e-0aae2 d16aa77)): java.rmi.RemoteException: ; nested exception is: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2] SQL0913N Unsuccessful execution caused by deadlock or timeout. Reason code "00C90088". SQLSTATE=57033 COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2] SQL0913N Unsuccessful execution caused by deadlock or timeout. Reason code "00C90088". SQLSTATE=57033Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 4.0 users of * * DB2 for zOS and OS/390 as their system * * adminstration repository. * **************************************************************** * PROBLEM DESCRIPTION: Multiple server startup caused * * deadlock in Naming Binding table with * * the following exception: * * COM.ibm.db2.jdbc.DB2Exception: [IBM] * * [CLI Driver][DB2] SQL0913N * * Unsuccessful execution caused by * * deadlock or timeout. Reason code * * "00C90088". SQLSTATE=57033 * **************************************************************** * RECOMMENDATION: * **************************************************************** Multiple server startup caused deadlock in Naming Binding table with the following exception: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2] SQL0913N Unsuccessful execution caused by deadlock or timeout. Reason code "00C90088". SQLSTATE=57033 This only happened while DB2 for zOS and OS/390 was used as the system adminstration repository for WebSphere Application Servers.Problem conclusion To prevent deadlock from happening, add a WITH KEEP RR UPDATE LOCKS clause at the end of SELECT ...FOR UPDATE SQLs. The clause is only supported and needed when a DB2 for zOS and OS/390 is used as the system adminstration repository.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 > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ84692
IBM Group: Software Group
Modified date: Mar 24, 2004
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.