|
Problem IC93177
|
Status: Closed |
STOPPING A FILE EVENT MONITOR MAY CAUSE DB2 TO MARK DATABASE BAD AND BRING INSTANCE DOWN |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
The db2diag.log could dump a message as follows:
2013-04-26-19.58.41.422235-300 I823663A547 LEVEL: Error
PID : <PID> TID : <TID> PROC : db2sysc 0
INSTANCE: <INST> NODE : 000 DB : <DB>
APPHDL : 0-3929 APPID: *LOCAL.x.x
AUTHID : <AUTHID>
EDUID : <EDUID> EDUNAME: db2agent (DB) 0
FUNCTION: DB2 UDB, database monitor, sqm_evmon_mgr::stop_evmon,
probe:121
CALLED : DB2 UDB, database monitor,
sqmEvmonWaiter::waitForEvmon
RETCODE : ZRC=0x83000004=-2097151996
DATA #1 : String, 10 bytes
<Event Monitor name>
-2097151996 translates to "Unexpected Operating System error".
The trap file generated after instance crash could have a stack
similar to the following:
<StackTrace>
-------Frame------ ------Function + Offset------
0x090000000063CAB0 pthread_kill + 0xB0
0x0900000009797890 sqloDumpEDU + 0x34
0x0900000009230AB8 sqldDumpContext__FP9sqeBsuEduiN42PCcPvT2 +
0xFC
0x0900000009D011B8
sqldDumpContext__FP9sqeBsuEduiN42PCcPvT2@glue5A7 + 0x98
0x0900000009D6EEDC sqlrr_dump_ffdc__FP8sqlrr_cbiT2 + 0x36C
0x090000000D418010 sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai + 0x50
0x090000000D4180F8 sqlzeDumpFFDC__FP8sqeAgentUiP5sqlcai@glue52F
+ 0x88
0x090000000D4185F0
sqlzeMapZrc__FP8sqeAgentUiUlT2P5sqlcaiPC12sqlzeContextb + 0x1A4
0x090000000D418F48 sqlrrMapZrc__FP8sqlrr_cbUiUli@glue3BD + 0x80
0x0900000009E069E0 sqlrienv_evm__FP8sqlrr_cbP10sqlz_valueT2 +
0x114
0x090000000D024450 sqlrienv__FP8sqlrr_cb + 0x68
0x090000000D2F2B84 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm +
0x28
0x090000000D4AE874 sqlrr_execute_immediate__FP8sqlrr_cbi + 0x544
0x090000000D4AE210
sqlrr_execimmd__FP14db2UCinterfaceP16db2UCprepareInfo + 0x25C
0x090000000D4ADEBC
sqljs_ddm_excsqlimm__FP14db2UCinterfaceP13sqljDDMObject + 0x850
0x090000000D4AD5FC
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
interface + 0x1C
0x090000000D2B371C
.sqljsParse.fdpr.clone.77__FP13sqljsDrdaAsCbP14db2UCinterfaceP8s
qeAgentb + 0x240
0x090000000D29BD44 @63@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb
+ 0xAA8
0x090000000D090658
@63@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA0
0x090000000D0902CC
@63@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x260
0x090000000D08FD94 sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T +
0x1EC
0x090000000D16E3D8 RunEDU__8sqeAgentFv + 0x298
0x090000000D163D58 EDUDriver__9sqzEDUObjFv + 0xE4
0x090000000D16BCFC sqloEDUEntry + 0x260
</StackTrace> |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v10.1 FP3. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Fixed in DB2 v10.1 FP3. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC95404 IC95406 IC95407 IC95408 IC95409 IC95410
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.06.2013
18.06.2014
18.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
