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 IC80024 Status: Geschlossen

DB2 may encounter 'deadlock' on system catalog SYSIBM.SYSCOLAUTH
when performing two DROP TABLE statements simultaneously.

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
Deadlocks on system catalog may occur when concurrently perform 
two DROP TABLE statements on two different tables. 
 
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      : SYSPLANDEP 
  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      : SYSCOLAUTH 
  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 9.5 on Linux, Unix and Windows          * 
* platforms.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Deadlocks on system catalog may occur when concurrently      * 
* perform two DROP TABLE statements on two different tables.   * 
*                                                              * 
* 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      : SYSPLANDEP                  * 
*   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      : SYSCOLAUTH                  * 
*   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                           * 
* =============================================                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW Version 9.5 FixPak 9 or higher levels.    * 
****************************************************************
Local-Fix:
Perform the two DROP TABLE statements sequentially.
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 LUW Version 9.5 FixPak 9.
Workaround
Perform the two DROP TABLE statements sequentially.
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC80424 IC84198 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.11.2011
12.03.2012
12.03.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.0.,
9.5.
Problem behoben lt. FixList in der Version
9.5.0.9 FixList