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

DB2SUPPORT -D <DB_NAME> MIGHT HANG BECAUSE OF LOCK HELD BY OTHER
APPLICATIONS ON SYSTEM CATALOG ROWS/TABLES

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Collecting db2support with -d option might hang at the following 
entry: 
 
      [Select count(*) from sysibm.systables where type='T' and 
creator ...] 
 
because of locks held by other applications on system catalog 
rows/tables
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 Fix Pack 9.                       * 
****************************************************************
Local Fix:
Use -nco option to avoid database connection
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 version 9.7 Fix Pack 9. 
Starting from this version isolation level used by db2support 
tool can be specified via "-il" switch, which previously was 
applicable only to optimizer mode ("-st", "-sf"). 
In order to avoid locking, db2support can be collected with 
uncommitted read (UR) isolation level, e.g. 
$ db2support . -d <db_name> -il UR
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC91488 IC95240 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.04.2013
16.12.2013
16.12.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