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

TIMEOUT IN DB2IUPDT MAY CAUSE OPERATION TO FAIL WITH "DBI1250E
APPLICATIONS ARE STILL USING THE INSTANCE"

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Running db2iupdt to complete a fixpak or special build 
installation may return 
 
DBI1250E Applications are still using instance <instance name> 
 
despite the fact that the instance was shutdown and it's 
proven that there are no db2 processes active anymore. 
 
This issue may be caused by a too low timeout value (10 seconds) 
currently used in function "chk_instance_stopped" in the 
db2iutil script which is called by db2iupdt. It's likely to be 
seen when updating a large DPF instance (large = number of 
partitions in db2nodes.cfg). 
 
If this issue applies in your environemnt run the db2gcf utility 
standalone: 
 
$ timex <DB2INSTALLPATH>/bin/db2gcf -i <instance> -s -t 10 -L 
 
and check if the command returns: 
 
db2gcf Error : GCF Module function failed. 
 
and needs more than 10 seconds to complete. 
Then you are affected by this APAR.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to Version 9.7 Fix Pack 6                             * 
****************************************************************
Local Fix:
N/A
available fix packs:
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
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
Problem was first fixed in Version 9.7 Fix Pack 6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.09.2011
02.08.2012
02.08.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList