DB2 FOR LUW / DB2FORLUW / A10 - DB2

The following snippet of code taken from the 
/usr/sbin/rsct/sapolicies/db2/db2V10_stop.ksh script shows that 
the db2gcf stop command is run with a 100 second timeout value: 
-------------------------------------------------------- 
else 
   su - ${DB2INSTANCE} -c "$INSTHOME/sqllib/bin/db2gcf -t 100 -d 
-p ${NN?} -i ${DB2INSTANCE?} -L" 
   rc=$? 
fi 
-------------------------------------------------------- 
If after 100 seconds, the instance is not successfully stopped 
then we proceed to kill the db2sysc process for the DB2 
partition in order to allow the partition failover to proceed. 
In some cases, the 100 second value may be set too low causing 
the DB2 partition to be killed prematurely. In order to address 
this, an environment variable "DB2GCF_STOP_TIMEOUT" has been 
introduced to allow this timeout value to be tuned by the 
customer.

Set the timeout value by setting the following environment 
variable as the instance owner: 
export DB2GCF_STOP_TIMEOUT=<value in seconds>

not known / see Local fix

Delivered via this APAR.

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

04.02.2015
13.07.2015
13.07.2015