Latest versionsfixlist
11.1.0.6 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC77204 Status: Closed

DB2 INSTANCE ABEND WHEN RUNNING NESTED PROCEDURES/ROUTINES

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
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
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* see ERROR DESCRIPTION                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 Fix Pack 9.                       * 
****************************************************************
Local Fix:
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)"
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.5 Fix Pack 9.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.06.2011
23.03.2012
23.03.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.