DB2 FOR LUW / DB2FORLUW / 970 - DB2

In a DPF environment, if an internal SQL statement is invoked 
from within a stored procedure, then there is a chance that it 
may crash with the following stack traceback: 
 
RollupCurrentMetrics 
stMetrics 
sqlmActivityExit 
sqlrr_activity_exe_stop 
sqlrr_dss_router 
sqlrr_subagent_router 
sqleSubRequestRouter 
sqleProcessSubRequest 
RunEDU 
EDUDriver 
sqlzRunEDU 
sqloEDUEntry 
 
An example of an internal SQL, and the one that lead to the 
discovery of this problem, would be if a module was created (see 
Info Center for "create module" command), and it defined the 
default SYS_INIT routine that gets executed  during module 
intialization.  In this case, if any routine that is defined in 
the module is run, DB2 will implicitly first execute the 
SYS_INIT routine as internal SQL. There may be other examples of 
internal SQL that could result in the same problem.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5                        * 
****************************************************************

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
 

First fixed in Version 9.7 Fix Pack 5.

keiner bekannt / siehe Local-Fix

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

11.07.2011
30.01.2012
30.01.2012

9.7.FP5