suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT16674 Status: Closed

In a pureScale environment, a DB2 member may crash following successive
cluster failures(alerts).

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
In a pureScale environment, a DB2 member may crash with the 
following stack: 
 
0x00007F72D49ED205 
_Z25ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvmm + 
0x0385 
                (/home/db2inst1/sqllib/lib64/libdb2osse.so.1) 
0x00007F72D49ECE0C ossDumpStackTraceV98 + 0x002c 
                (/home/db2inst1/sqllib/lib64/libdb2osse.so.1) 
0x00007F72D49E7F0D _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 
0x00fd 
                (/home/db2inst1/sqllib/lib64/libdb2osse.so.1) 
0x00007F72DAE8C194 sqlo_trce + 0x0404 
                (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007F72DAEE16CA sqloEDUCodeTrapHandler + 0x027a 
                (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x000000300100F710 address: 0x000000300100F710 ; dladdress: 
0x0000003001000000 ; offset in lib: 0x000000000000F710 ; 
                (/lib64/libpthread.so.0) 
0x0000003000432635 gsignal + 0x0035 
                (/lib64/libc.so.6) 
0x0000003000433E15 abort + 0x0175 
                (/lib64/libc.so.6) 
0x0000003000470547 address: 0x0000003000470547 ; dladdress: 
0x0000003000400000 ; offset in lib: 0x0000000000070547 ; 
                (/lib64/libc.so.6) 
0x0000003000475E76 address: 0x0000003000475E76 ; dladdress: 
0x0000003000400000 ; offset in lib: 0x0000000000075E76 ; 
                (/lib64/libc.so.6) 
0x00000030004789B3 address: 0x00000030004789B3 ; dladdress: 
0x0000003000400000 ; offset in lib: 0x00000000000789B3 ; 
                (/lib64/libc.so.6) 
0x00007F72D49CDB16 _ossMemFree + 0x0126 
                (/home/db2inst1/sqllib/lib64/libdb2osse.so.1) 
0x00007F72D5F3601E 
_Z37sqlhaDeleteClusterObjectListStructureP25SQLHA_CLUSTER_OBJECT 
_LIST + 0x025e 
                (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007F72D9A2AFBB 
_Z20sqlhaSysIBMGetAlertsPP17sqlerDB2AlertDataPjP5sqlcaP19SQLHA_C 
ONTROL_BLOCK + 0x058b 
                (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007F72D81ECE7A _Z29sqlerTrustedRtnCallbackRouterjPPv + 
0x0afa 
                (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007F616155BFE1 db2_instance_alerts + 0x0231 
 
(/home/db2inst1/sqllib/bin/routine/db2dbrouttrusted) 
0x00007F72D8F130B7 sqloInvokeFnArgs + 0x6fd7 
                (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
0x00007F72DBEF2A71 
_Z19sqlriInvokerTrustedP10sqlri_ufobP21sqlriRoutineErrorIntfb + 
0x2071 
                (/home/db2inst1/sqllib/lib64/libdb2e.so.1) 
 
If it is found that a DB2 member has crashed with above stack, 
then this APAR has been hit. 
 
Another symptom is db2rocme crash with following stack. In this 
case, DB2 member does not crash. 
 
leftmost 
malloc_y 
malloc_common 
malloc 
strdup 
sqlhaHostnameComp 
sqlhaCheckNetworkAdapterOnHost 
sqlhaGetAlertResources 
sqlhaSysIBMGetAlerts 
rocmDb2clusterActionDisplayAlerts 
rocmDoDb2clusterEngineAction 
main
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fix Pack 6                               * 
****************************************************************
Local Fix:
N/A
Solution
First fixed in DB2 10.1 Fix Pack 6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.08.2016
02.03.2017
02.03.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)