DB2 FOR LUW / DB2FORLUW / A10 - DB2

Database might crash with SIGSEGV signal during query involving 
casting i.e. ( bigint( timestamp ). 
 
Generated trap file will contain entries similar to the 
following: 
Signal #11 (SIGSEGV): si_addr is 0xFFFFFFF990000000, si_code is 
0x00000001 (SEGV_MAPERR:Address not mapped to object.) 
and under <ProcessObjects> there will be shared memory segment 
listed where upper boundary address is equal to si_addr from 
above entry, in this example equals to 0xFFFFFFF990000000. 
0xfffffff980000000-0xfffffff990000000    262144K rwxs Shared 
memory id = 1711276035 (0x66000003) 
 
The top of the stack trace have strncat() function, and stack 
trace might look similar to the following: 
 
<StackTrace> 
strncat(0xd,0x80160000,0x0,0xfffffffa80715370,0x40,0xfffffffae5b 
f6144) + 0x40 
sqlv_chr_2_num(0xd,0x80160000,0x0,0xfffffffa80715370,0x40,0xffff 
fffae5bf6144) + 0x694 
sqlri_char2int(0xfffffffb3eeb6020,0x1400,0x0,0xfffffffa80715370, 
0x0,0xffffffff7c2cf138) + 0xf4 
sqldEvalDataPred(0xffffffff47126e10,0xfffffffae5bf6458,0xfffffff 
a80715330

No local fix

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 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
 

not known / see Local fix

This APAR is a duplicate of IC84180

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

14.06.2012
04.12.2012
04.12.2012