Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC66624 Status: Closed

CONCURRENT CREATE EVENT MONITOR STATEMENTS DEADLOCK

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Concurrently executing CREATE EVENT MONITOR statements may 
deadlock.  Deadlock event monitor output shows that both 
statements are holding row locks in SYSIBM.SYSTABLES that the 
other application is requesting.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 Version 9.7 GA through to Fix Pack 1 servers on      * 
* Linux, Unix and Windows platforms executing concurrent       * 
* create event monitor statements.                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Create event monitor statements which are defined to make    * 
* use of tables (either explicitly specified in the create     * 
* statement, or implicitly defined based on the event monitor  * 
* name), need to create these tables as part of the statement. * 
* Incorrect isolation levels while scanning SYSIBM.SYSTABLES   * 
* to carry out the necessary logic lead to the possibility of  * 
* deadlocks.                                                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Avoid creating event monitors concurrently, or apply DB2     * 
* Version 9.7 Fix Pack 2.                                      * 
****************************************************************
Local Fix:
Ensure that applications are not creating event monitors 
concurrently.
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem first fixed in DB2 Version 9.5 Fix Pack 6 and all 
subsequent Fix Packs.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC66789 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.02.2010
25.05.2010
25.05.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6,
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList