home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC76305 Status: Closed

DB2 MIGHT ENCOUNTER 'DEADLOCK' ERROR WHEN PERFORMING TWO DROP
TABLE STATEMENTS SIMULTANEOUSLY.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When concurrently perform two DROP TABLE statements on different 
tables but with similar namings, the two statements may lead to 
various kinds of deadlocks: 
-- deadlock among the catalog tables, SYSIBM.SYSVIEWDEP and 
SYSIBM.SYSTABAUTH 
-- deadlock among the catalog tables, SYSIBM.SYSVIEWS and 
SYSIBM.SYSVIEWS 
The problem is more likely to happen if the tables being dropped 
have dependent views and other objects (e.g. index or trigger) 
defined on it. 
 
To identify the problem, you need to use DB2 event monitor to 
collect detailed information for deadlocks. 
When the deadlock error occurs, in the event monitor output you 
will see the following entries: 
============================================= 
  Table of lock waited on      : SYSVIEWDEP 
  Schema of lock waited on     : SYSIBM 
  Type of lock: Row 
  Mode of lock: X   - Exclusive 
  Mode application requested on lock: S   - Share 
    Text     : drop table NEWTON.T1 
 
  Table of lock waited on      : SYSTABAUTH 
  Schema of lock waited on     : SYSIBM 
  Type of lock: Row 
  Mode of lock: U   - Update 
  Mode application requested on lock: X   - Exclusive 
    Text     : drop table NEWTON.T2 
============================================= 
or 
============================================= 
  Table of lock waited on      : SYSVIEWS 
  Schema of lock waited on     : SYSIBM 
  Type of lock: Row 
  Mode of lock: U   - Update 
  Mode application requested on lock: U   - Update 
    Text     : drop table NEWTON.T1 
 
  Table of lock waited on      : SYSVIEWS 
  Schema of lock waited on     : SYSIBM 
  Type of lock: Row 
  Mode of lock: X   - Exclusive 
  Mode application requested on lock: U   - Update 
    Text     : drop table NEWTON.T2 
============================================= 
or 
============================================= 
  Table of lock waited on      : SYSVIEWS 
  Schema of lock waited on     : SYSIBM 
  Type of lock: Row 
  Mode of lock: U   - Update 
  Mode application requested on lock: X   - Exclusive 
    Text     : drop table NEWTON.T1 
 
  Table of lock waited on      : SYSVIEWS 
  Schema of lock waited on     : SYSIBM 
  Type of lock: Row 
  Mode of lock: U   - Update 
  Mode application requested on lock: U   - Update 
    Text     : drop table NEWTON.T2 
=============================================
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 9.7 on Linux, Unix and Windows          * 
* platforms.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 9.7 FixPak 6 or higher levels.    * 
****************************************************************
Local Fix:
Perform the two DROP TABLE statements sequentially.
available fix packs:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 UDB Version 9.7 FixPak 6.
Workaround
Perform the two DROP TABLE statements sequentially.
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC84554 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.05.2011
11.06.2012
11.06.2012
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList
9.7.0.6 FixList