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 IC79697 Status: Geschlossen

DATABASE MIGHT CRASH WITH SIGSEGV SIGNAL DURING QUERY INVOLVING CASTING.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 9.7 FixPack 6.                    * 
****************************************************************
Local-Fix:
No local fix
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 6 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
Problem was first fixed in DB2 UDB Version 9.7 FixPack 6.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC84180 IC84443 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.11.2011
06.06.2012
06.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList