DB2 - Problem description
| Problem IT06177 | Status: Closed |
In rare cases, DB2 instance may trap when STMM thread is shutting down | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
Symptom:
There would be a db2stmm's Error and an associated FODC_Trap...
message on db2diag.log as similar as below.
...
2014-12-17-04.19.23.472402+540 I61305E570 LEVEL: Error
PID : 17093 TID : 46912837249344PROC :
db2sysc
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-13247 APPID: *LOCAL.DB2.141216191620
AUTHID : DB2INST1
EDUID : 5411 EDUNAME: db2agent (idle)
FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh,
probe:10
MESSAGE : Error in agent servicing application with APPLICATION
NAME:
DATA #1 : Hexdump, 7 bytes
0x0000000202E66852 : 6462 3273 746D 6D
db2stmm
2014-12-17-04.19.23.476208+540 I61876E220 LEVEL: Severe
PID:17093 TID:46912837249344 NODE:000 Title: sqeAgent
Dump File:
/.../db2dump/FODC_Trap_2014-12-17-04.19.23.267764_0000/17093.541
1.000.dump.bin
...
From the associated 17093.5411.000.trap.txt in the FODC_Trap...
directory, may find similar stack trace backs as below.
...
<POFDisassembly>
_Z25sqlplCalculateLmaxTriggerP16sqeLocalDatabasemb + 0x0013
(/.../sqllib/lib64/libdb2e.so.1)
0x00002AAAABE094B1 : 4C8BA8188C00004D
</POFDisassembly>
<StackTrace>
-----FUNC-ADDR---- ------FUNCTION + OFFSET------
0x00002AAAB0407C8B ossDumpStackTraceEx + 0x01ef
0x00002AAAB0402A4A _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm +
0x00cc
0x00002AAAAD37C6DB sqlo_trce + 0x03fb
0x00002AAAAD3C54D1 sqloEDUCodeTrapHandler + 0x0265
0x0000003B2E80ECA0 address: 0x0000003B2E80ECA0 ; dladdress:
0x0000003B2E800000 ; offset in lib: 0x000000000000ECA0 ;
0x00002AAAABE094B1
_Z25sqlplCalculateLmaxTriggerP16sqeLocalDatabasemb + 0x0013
0x00002AAAAC0634A2
_Z42stmmCleanupMemConsumersOnTunerDeactivationP16sqeLocalDatabas
e + 0x0038
0x00002AAAAC063018
_Z31stmmDeactivateTuningIfNecessaryP16sqeLocalDatabasebbb +
0x0102
0x00002AAAAC063561
_Z35stmmUpdateSTMMStateOnDaemonShutdownP16sqeLocalDatabase +
0x007f
0x00002AAAAC062477 stmmMemoryTunerMain + 0x0297
0x00002AAAAB95B801 _Z26sqleIndCoordProcessRequestP8sqeAgent +
0x04c5
0x00002AAAAB968719 _ZN8sqeAgent6RunEDUEv + 0x038f
0x00002AAAAC05C9B8 _ZN9sqzEDUObj9EDUDriverEv + 0x00a6
0x00002AAAAC05C90F _Z10sqlzRunEDUPcj + 0x0009
0x00002AAAABDC2150 sqloEDUEntry + 0x02f4
0x0000003B2E80683D address: 0x0000003B2E80683D ; dladdress:
0x0000003B2E800000 ; offset in lib: 0x000000000000683D ;
0x0000003B2DCD503D clone + 0x006d
</StackTrace>
...
Condition of problem:
Any situation where STMM is ON. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 UDB Version 9.7 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.7 FixPack 11. * **************************************************************** | |
| Local Fix: | |
Trun off self_tuning_mem db cfg parameter. | |
| Solution | |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 11. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 18.12.2014 13.10.2015 13.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 |
|