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

DB2STOP FORCE HANGS WHEN INSTANCE IS QUIESCED IN RESTRICTED ACCESS

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
db2stop force hangs when the instance is quiesced in restricted 
access. 
 
Following messages are seen in the db2diag.log 
 
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:270 
DATA #1 : String, 26 bytes 
Active EDUs to be waited : 
DATA #2 : unsigned integer, 4 bytes 
22
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V10.1                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V10.1 FP3                                         * 
****************************************************************
Local Fix:
Deactivate the databases or unquiesce the instance
available fix packs:
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

Solution
First fixed in DB2 V10.1 FP3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.09.2013
18.10.2013
18.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList