DB2 - Problembeschreibung
Problem IT06964 | Status: Geschlossen |
DURING AN AUTOMATED PARTITION STOP, THE DB2GCF STOP COMMAND TIMES OUT LEADING TO THE INSTANCE BEING KILLED PREMATURELY | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
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. | |
Problem-Zusammenfassung: | |
Local-Fix: | |
Set the timeout value by setting the following environment variable as the instance owner: export DB2GCF_STOP_TIMEOUT=<value in seconds> | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Kommentar | |
Delivered via this APAR. | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 04.02.2015 13.07.2015 13.07.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.5 |