DB2 FOR LUW / DB2FORLUW / 970 - DB2

If you get crashes or unexpected behavior, this APAR could be at 
fault. 
One of the scenarios when this issue can happen is if you are 
using compiled triggers. 
 
If you are using DB2MEMDBG db2set regisrty, in the case of 
compiled triggers, the stack may be similar to: 
 
 
sqlriMemValidate 
sqlriValidateSection 
sqlriSectInvoke 
sqlrr_process_execute_request 
sqlrr_execute 
sqljs_ddm_excsqlstt 
sqljsParseRdbAccessed 
sqljsParse

**************************************************************** 
* USERS AFFECTED:                                              * 
* Statements involving compiled SQL triggers.                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Crash if DB2MEMDBG options is used, or wrong results, due to * 
* section memory overwrite because of use of compiled SQL      * 
* triggers.                                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply 97FP4 with the fix.                                    * 
****************************************************************

Apply code fix.

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

Apply 97FP4 with the fix.

keiner bekannt / siehe Local-Fix

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

09.11.2010
29.04.2011
29.04.2011

9.7.FP4