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

IN RARE TIMING SCENARIOS DB2 TERMINATE MAY SEGFAULT AFTER A RESTORE
OPERATION.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
After a Restore operation is performed, a subsequent db2 
terminate may hang or segfault. The problem is caused by some 
erroneous lock related book-keeping. 
 
The stack dump may have the following entries from 
sqlpTermAgent()->sqlplfre()->sqlo_xlatch::getIdentity() 
 
</Siginfo_t> 
Signal #11 (SIGSEGV): si_addr is 0x0000002C00000014, si_code is 
0x00000001 (SEGV_MAPERR:Address not mapped to object.) 
</SignalDetails> 
 
---FUNC-ADDR---- ------FUNCTION + OFFSET------ 
0000002A9B8C9157 ossDumpStackTraceEx + 0x01f7 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.3/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2osse.so.1) 
0000002A9B8C4CCC _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 0x00b4 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.3/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2osse.so.1) 
0000002A9B8C4D93 _ZN11OSSTrapFile4dumpEmiP7siginfoPv + 0x0009 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.3/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2osse.so.1) 
0000002A97C8ABCF sqlo_trce + 0x03f3 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.3/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A97D08FDD sqloEDUCodeTrapHandler + 0x0107 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.3/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A956784F0 address: 0x0000002A956784F0 ; dladdress: 
0x0000002A9566C000 ; offset in lib: 0x000000000000C4F0 ; 
                (/lib64/tls/libpthread.so.0) 
0000002A968428DC _ZNK12sqloSpinLock11getIdentityEv + 0x0000 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.3/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A9684297A _ZNK11sqlo_xlatch11getIdentityEv + 0x0006 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.3/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A97DA3545 _Z8sqlplfreP8sqeAgentP8SQLP_LCBP8SQLP_LRBm + 
0x05d9 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.3/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A97D571AF _Z13sqlpTermAgentP8sqeAgentm + 0x010d
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 LUW Users                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In rare timing scenarios DB2 TERMINATE may segfault after a  * 
* RESTORE operation.                                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Customer need to upgraded to  db2_v97fp3                     * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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
db2_v97fpbin will contain the fix . After a Restore operation 
isperformed, a subsequent db2 terminate will not hang or 
segfault
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.04.2010
11.11.2010
11.11.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
9.7.0.3 FixList
9.7.0.3 FixList