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 IT06746 Status: Closed

DB2 MAY CRASH WITH SIGNAL #11(SIGSEGV) AFTER UPGRADING TO V97FP10 FROM
BELLOW FIXPACK LEVEL

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 may crash after upgrading to V97fp10 from below fixpack 
level due to the changes made in statistical/activity monitor 
tables. If you have Statistics/Activity monitor defined from 
fixpacks below v97fp10 and then upgrade to v97fp10,DB2 may 
crash. 
 
Trap file will have Signal info as bellow: 
 
</Siginfo_t> 
Signal #11 (SIGSEGV): si_addr is 0x0000000000000000, si_code is 
0x00000080 (SI_KERNEL:Send by kernel.) 
</SignalDetails> 
 
Stack in trap will be as bellow: 
Stack #1             Signal #11        Timestamp 
2015-01-14-06.40.01.039691 
0 > ossDumpStackTraceEx 
1 > OSSTrapFile::dumpEx 
2 > sqlo_trce 
3 > sqloEDUCodeTrapHandler 
4 > _IO_ftrylockfile 
5 > sqmRequestMetrics::populateOldEvmonMetricsDvalues 
6 > sqm_evmon_ttarget::write_data 
7 > sqm_evmon_target::prepAndWriteData 
8 > sqmEvmonBuffer::write_data 
9 > sqmEvmonWriter::evmonWriter 
10 >-- sqmEvmonWriter::startMeUp 
11 >-- sqlm_bds_start_monitor_hdl 
12 >-- sqleSubRequestRouter 
13 >-- sqleProcessSubRequest 
14 >-- sqeAgent::RunEDU 
15 >-- sqzEDUObj::EDUDriver 
16 >-- sqlzRunEDU 
17 >-- sqloEDUEntry 
18 >-- __deallocate_stack 
19 >-- __clone 
 
You will see similar error logs in db2diag.log: 
 
2015-01-14-06.40.01.115961+000 I9575182E571        LEVEL: Severe 
PID     : 1894                 TID  : 46912854026560PROC : 
db2sysc 39 
INSTANCE: bculinux             NODE : 039          DB   : 
BDWLP01 
APPHDL  : 0-75                 APPID: *N0.DB2.150114063059 
AUTHID  : BCULINUX 
EDUID   : 102                  EDUNAME: db2evmtp (DB2STATISTICS) 
39 
FUNCTION: DB2 UDB, RAS/PD component, 
pdResilienceIsSafeToSustain, probe:800 
DATA #1 : String, 37 bytes 
Trap Sustainability Criteria Checking 
DATA #2 : Hex integer, 8 bytes 
0x2000000000021009 
DATA #3 : Boolean, 1 bytes 
false
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 11.                      * 
****************************************************************
Local Fix:
Drop and Recreate the event monitor tables to avoid further 
crashes.
Solution
First fixed in DB2 Version 9.7 Fix Pack 11.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.01.2015
06.10.2015
06.10.2015
Problem solved at the following versions (IBM BugInfos)
9.7.FP11
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.11 FixList