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

'LIST TABLESPACES SHOW DETAIL' COMMAND IN DB2SUPPORT TOOL MAY CA
USE DB2SUPPORT TO HANG IF DATABASE IS IN SET WRITE SUSPEND MODE

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
db2support tool currently runs "list tablespaces show detail" 
and "list tablespace containers" commands, both of which are 
deprecated since v9.7. 
 
The "list tablespaces show detail" command will hang if "set 
write suspend on database" has also been issued on the database, 
due to a change in latching protocol since DB2 v10.1. 
This may cause the db2support tool to hang as well in such 
situation. 
 
db2support also runs db2pd -tablespaces -alldbs on UNIX. This 
will be extended to Windows environment as well to collect the 
tablespace related data. With this APAR, the deprecated commands 
are removed from the db2support utility.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Environments using DB2 LUW v10.1 Fixpack 4 and older         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v10.1 Fix Pack 5 or higher.               * 
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.02.2015
05.02.2016
05.02.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList