home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC84554 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 10.1 on Linux, Unix and Windows         * 
* platforms.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 10.1 FixPak 1 or higher levels.   * 
****************************************************************
Local-Fix:
Perform the two DROP TABLE statements sequentially.
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 UDB Version 10.1 FixPak 1.
Workaround
Perform the two DROP TABLE statements sequentially.
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.06.2012
23.06.2013
23.06.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList