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 IC89995 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 9.7 on Linux, Unix and Windows          * 
* platforms.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 LUW Version 9.7 Fix Pack 9 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.
available fix packs:
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 LUW Version 9.7 Fix Pack 9.
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.
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC90269 IC91791 IC95428 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.02.2013
08.10.2013
08.10.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.9 FixList
9.7.0.9 FixList