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

SIGNAL #11 SIGSEGV CRASH CALLING CONVERTTO64BIT FROM SNAPSHOT_LOCK

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See ERROR DESCRIPTION.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 Fix Pack 2 or higher.                   * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

Lösung
Problem first fixed in DB2 V10.1 Fix pack 2 .  This is a server 
side fix and should be applied to the DB2 database server.
Workaround
See LOCAL FIX.
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.11.2012
19.04.2013
19.04.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.2 FixList
10.5.0.2 FixList