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 IC80377 Status: Closed

SIGNAL #11 SIGSEGV CRASH CALLING CONVERTTO64BIT FROM SNAPSHOT_LOCK

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
When calling SYSPROC.SNAPSHOT_LOCK the db2fmp process used to 
run non-SQL stored procedures and user defined functions may 
abnormally terminate with a segmentation fault or signal #11 
with the following 
stack: 
 
ossDumpStackTraceEx 
OSSTrapFile6dumpExEmiP7siginfoPvm 
OSSTrapFile4dumpEmiP7siginfoPv 
sqlo_trce 
sqlo_dari_trca 
offset in lib: 0x000000000000EB10 ; 
convertTo64bitP16sqlm_header_dataPlPs 
snapshot_lock 
sqloInvokeFnArgs 
offset in lib: 0x0000000000AE1086 ; 
sqlerDyload 
sqlerFmpListener 
main
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See ERROR DESCRIPTION.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply v9.5 Fixpack 8.                                        * 
****************************************************************
Local Fix:
Solution
Problem was first fixed in v9.5 Fixpack 8.  This is a server 
side fix and should be applied to the DB2 database server.
Workaround
See LOCAL FIX.
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC83532 IC87857 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.12.2011
30.10.2012
30.10.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.10 FixList