home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC77201 Status: Geschlossen

DB2 INSTANCE ABEND WHEN RUNNING NESTED PROCEDURES/ROUTINES

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* see ERROR DESCRIPTION                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5.                       * 
****************************************************************
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)"
verfügbare FixPacks:
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

Lösung
First fixed in DB2 Version 9.7 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC77204 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.06.2011
04.11.2011
04.11.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList