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

'LOAD QUERY' COMMAND ENCOUNTERS SQL6024C AND HOLD LOCKS ON
CATALOG TABLES

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
When 'LOAD QUERY' command encounters SQL6024C, it will keep 
holding locks on catalog tables such as 
"SYSIBM.SYSPARTITIONMAPS" and "SYSIBM.SYSTABLES", until the next 
COMMI/ROLLBACK statement is performed. 
 
Here is an example of the problem reproduced by DB2 CLP: 
=========================================== 
db2 "load query table tmp_1_2_3" 
SQL6024C  Table or index "TMP_1_2_3" is not defined on node "0". 
 
db2pd -db sample -locks showlocks -alldbpartitionnums 
Locks: 
Address            TranHdl    Lockname                   Type 
Mode Sts Owner      Dur HoldCount  Att        ReleaseFlg rrIID 
0x07000000305F0780 2          0000002A000000000000000054 Table 
.IS  G   2          1   0          0x00003010 0x40000000 0 
TbspaceID 0     TableID 42 
0x07000000305F0680 2          00000005000000000000000054 Table 
.IS  G   2          1   0          0x00003000 0x40000000 0 
TbspaceID 0     TableID 5 
=========================================== 
 
This might result in SQL0911N in case other applications need to 
access the catalog tables at the same time.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 10.1 on Linux, Unix and Windows         * 
* platforms.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 LUW Version 10.1 Fix Pack 3 or higher levels.  * 
****************************************************************
Local-Fix:
1. Release locks by issuing a ROLLBACK statement in the 
application that is holding the locks. 
2. Force off the application that is holding the locks.
verfügbare FixPacks:
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 LUW Version 10.1 Fix Pack 3.
Workaround
1. Release locks by issuing a ROLLBACK statement in the 
application that is holding the locks. 
2. Force off the application that is holding the locks.
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.02.2013
07.10.2013
07.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList