home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC89859 Status: Closed

DB2 MAY ABEND WHEN USING DB2 TEXT EXTENDERS

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
A rare timing condition involving loading/unloading of the DB2 
client library when using DB2 text extenders may cause a DB2 
instance to shutdown abnormally (trap).   The trap symptoms may 
vary and are similar to memory corruption.  Examples: 
 
_getpwnam_shadow_r 
_posix_getpwnam_shadow_r 
osshomepath.getpwnam_r 
ossBuildHomeDirectoryRelativePath 
GlobalReg.GetGlobalRegPathnameInternal 
GlobalReg::init 
GlobalReg::GlobalReg 
ossOpenInstanceList 
EnvRegRefresh 
EnvRegOpen 
sqloPRegQueryDefaultValue 
EnvGetDB2SysVar 
EnvQueryDB2SystemVariables 
sqloInitEnvironment 
.sqloAppLibInit 
mod_init1 
usl_init_mods 
uload 
load1 
load 
loadAndInit 
dlopen 
sqloAIXLoadModuleTryShr 
sqloLoadModule 
sqlerLibraryLoad 
.sqlerRoutineLoad 
.sqlriOneTimeInitRtn1Trusted 
sqlriOneTimeInitRtn 
... 
 
sqleAddToFreeCtxList 
sqleFreeTrustedCtxInternal 
sqleUCtrustedRtnTerm 
sqlerLibraryTrueUnload 
sqlerLibraryUnloadAll 
sqlri_close_udf_eog 
sqlrr_appl_term 
...
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Systems running DB2 Text Extenders                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 3                       * 
****************************************************************
Local Fix:
A workaround is to invoke a trusted routine over a persistent 
connection.  This will keep the client library loaded in the db2 
server process, thus avoiding the timing condition. 
db2 connect to <database> 
db2 "values dayofyear(current timestamp)" 
< leave this connection open continuously >
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem first fixed in DB2 Version 10.1 Fix Pack 3
Workaround
see Local Fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.01.2013
04.12.2013
04.12.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList