DB2 - Problem description
| Problem IT02193 | Status: Closed |
DPF: EVENT MONITOR APPLICATION IN PENDING REMOTE REQUEST - UNABLE TO FORCE. | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
Event monitor application might hang with the following
symptoms:
1. User unable to force off Event monitor application (might
have some locks on user tables which cause contention)
2. Coordinator agent is on Pending RemoteRequest state.
Stack of Coordinator agent might show the following:
sqloWaitEDUWaitPost
sqkfChannel::WaitRecvReady
sqkfChannel::ReceiveBuffer
sqkdBdsBufferTable::dequeueBuffer
sqkdBdsBufferTable::getNextBuffer
address: 0x00002AAAACAC07D2 ; dladdress:
address: 0x00002AAAACAC05E9 ; dladdress:
address: 0x00002AAAACAC0B84 ; dladdress:
sqlkdReceiveReply
sqleReceiveAndMergeReplies
sqlkdInterrupt
sqleDssStopUsing
sqeApplication::ForwardStopRequest
sqeApplication::AppStopUsing
address: 0x00002AAAABB73AE3 ; dladdress:
address: 0x00002AAAABB73982 ; dladdress:
sqleIndCoordProcessRequest
3. Active subagents on other partitions will show the following
stack:
sqloWaitEDUWaitPost
sqmEvmonWaiter::waitForEvmon
sqm_evmon_mgr::start_evmon
sqlm_bds_start_monitor_hdl
sqleSubRequestRouter
sqleProcessSubRequest
sqeAgent::RunEDU
sqzEDUObj::EDUDriver
sqlzRunEDU
sqloEDUEntry
4. db2diag.log will have entries like the following:
FUNCTION: DB2 UDB, base sys utilities,
sqeAgentServices::RequestAgentForAppl, probe:6
MESSAGE : Error processing app entry... SQLCODE =
DATA #1 : Hexdump, 4 bytes
0x00002AAAC2FF2248 : 48FC FFFF
H...
and
FUNCTION: DB2 UDB, database monitor, sqmEvmonWriter::startMeUp,
probe:71
MESSAGE : ZRC=0x800D0003=-2146631677=SQLM_ACT_INTRP
"Event monitor activation interrupted"
DIA8003C The interrupt has been received.
DATA #1 : String, 16 bytes | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 and Fix Pack 5 * **************************************************************** | |
| Local Fix: | |
Database has to be restarted to clear out the Event monitor application. | |
| Solution | |
Problem was first fixed in DB2 Version 10.1 and Fix Pack 5 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.06.2014 13.07.2015 13.07.2015 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.5 |
|