DB2 FOR LUW / DB2FORLUW / 970 - DB2

This problem happens if there has been an abnormal application 
connection failure caused for example by a memory allocation 
failure, where the database has been activated with all the 
async-EDUs up and running, but agent initialization fails. The 
problem is that there exists a small timing window where the 
failed agent can become the last agent connected to the 
database, and will be handling the database deactivation task. 
When that happens, due to the failed initialization the database 
will not be deactivated properly, causing some async-EDUs to be 
left behind without properly terminated. When this issue 
happens, the db2stop force process will be hanging on the 
following stack: 
 
waitid 
waitpid 
sqlowchd 
sqloexec2 
sqleStartStopSingleNode 
sqleIssueStartStop 
sqleProcessStartStop 
main 
 
The db2diag.log will show that the system controller keeps 
waiting on some active EDUs: 
 
2011-06-02-13.32.42.517358-240 I7277360E388       LEVEL: Event 
PID     : 28643                TID  : 2           PROC : db2sysc 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 2                    EDUNAME: db2sysc 
FUNCTION: DB2 UDB, oper system services, 
sqloSystemControllerMain, probe:270 
DATA #1 : String, 26 bytes 
Active EDUs to be waited : 
DATA #2 : unsigned integer, 4 bytes 
24

**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* see error description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Avoid the out-of-memory condition by increasing the amount   * 
* of physical memory on the system                             * 
****************************************************************

The instance will have to be shutdown by killing the process

DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 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
 

v97 fp 5

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

27.07.2011
28.02.2012
28.02.2012

9.7.FP5