Fixes are available
APAR status
Closed as program error.
Error description
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
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * DB2 LUW * **************************************************************** * PROBLEM DESCRIPTION: * * In rare timing scenarios DB2 TERMINATE may segfault after a * * RESTORE operation. * **************************************************************** * RECOMMENDATION: * * Customer need to upgraded to db2_v95fp5 * ****************************************************************
Problem conclusion
db2_v95fpbin will contain the fix . After a Restore operation is performed, a subsequent db2 terminate will not hang or segfault
Temporary fix
Comments
APAR Information
APAR number
LI75366
Reported component name
DB2 UDE ESE LIN
Reported component ID
5765F4104
Reported release
950
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-03-12
Closed date
2010-06-24
Last modified date
2010-06-24
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
IC68207 IC68208
Fix information
Fixed component name
DB2 UDE ESE LIN
Fixed component ID
5765F4104
Applicable component levels
R950 PSN
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
24 June 2010