DB2 FOR LUW / DB2FORLUW / A10 - DB2

Running db2iupgrade/db2iupdt to complete a upgrade, 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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All UNIX/Linux Platforms                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 Fixpack 3 or Higher                     * 
****************************************************************

Can edit the <DB2 Installation>/instance/db2iutil and remove the 
-t 10 from the call to db2gcf command checks.

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
 

Fixed in DB2 v10.1 Fixpack 3

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC95447 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

20.05.2013
27.09.2013
27.09.2013