DB2 FOR LUW / DB2FORLUW / 970 - DB2

This problem impacts DB2 systems executing nested routines on 
the UNIX platform only. 
 
When running nested procedures/routines, memory allocations 
meant for the persistent server-side memory area may become 
allocated from the non-persistent client-side memory area (used 
when trusted routines are executed).  The client-side memory 
area becomes freed when there are no longer any agents with 
cached trusted routines, which typically occurs only on systems 
with lower levels of activity (agents cached routines for the 
life of a connection).  Memory allocations allocated incorrectly 
from the client side may become invalid, causing a trap when 
they are subsequently accessed. 
 
Known vulnerable trusted DB2 routines include : 
ADMIN_LIST_HIST ( also called when accessing the DB_HISTORY 
admin view ) 
DB_GET_CFG ( also called when accessing the DBCFG admin view ) 
 
DB2 trap files may contain call stacks similar to the following 
: 
sqloCrashOnCriticalMemoryValidationFailure 
sqlofmblkEx 
sqlddFreeDD 
sqlddFreeDD 
sqljParseDsc 
 
sqloCrashOnCriticalMemoryValidationFailure 
sqlofmblkEx 
sqldReleaseWorkAreaMem 
sqldTermAgent

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* see ERROR DESCRIPTION                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5.                       * 
****************************************************************

Creating a persistent connection on each partition and executing 
a trusted routine will keep the client-side memory area active 
within the server process, preventing memory from becoming 
invalid. 
 
export DB2NODE=<db partition> 
db2 connect to <database> 
db2 values dayofweek"(current timestamp)"

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

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC77204 
follow-up : 

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

28.06.2011
04.11.2011
04.11.2011

9.7.FP5