DB2 - Problem description
| Problem IC68720 | Status: Closed |
DEADLOCK EVENT MONITOR MAY GET STUCK IN "PENDING REMOTE" STATUS IF GLOBAL EVENT MONITOR RUNS OUT OF DATABASE MONITOR HEAP. | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
For DPS system , if global event monitor run out of "Database
Monitor Heap" memory during event monitor activation. It can
stuck in "Pending remote" status.
Here is the example of the "db2 list applications global show
detail"
CONNECT Auth Id
Application Name Appl. Application Id
Seq# Number of Coordinating DB
Coordinator Status Status Change
Time DB Name DB Path
Handle
Agents partition number
pid/thread------------------------------------------------------
----------------------------------------------------------------
----------
-------------------- ----------
--------------------------------------------------------------
----- ---------- ---------------- ---------------
------------------------------ --------------------------
-------- --------------------
DB2INST1
db2taskd 53 *N0.DB2.100416004033
00001 1 0
26 Connect Completed Not Collected
SAMPLE /export/home/db2inst1/db2inst1/NODE0000/SQL00001/
DB2INST1
db2wlmd 54 *N0.DB2.100416004034
00001 1 0
27 Connect Completed Not Collected
SAMPLE /export/home/db2inst1/db2inst1/NODE0000/SQL00001/
DB2INST1
db2evmg_DB2DETAILDEA 58 *N0.DB2.100416004113
00002 3 0
34 Pending remote request Not Collected
SAMPLE /export/home/db2inst1/db2inst1/NODE0000/SQL00001/
DB2INST1
db2evmg_DB2DETAILDEA 59 *N0.DB2.100416004116
00004 3 0
35 Pending remote request Not Collected
SAMPLE /export/home/db2inst1/db2inst1/NODE0000/SQL00001/
DB2INST1
db2evmg_DB2DETAILDEA 60 *N0.DB2.100416004119
00006 3 0
36 Pending remote request Not Collected
SAMPLE /export/home/db2inst1/db2inst1/NODE0000/SQL00001/ | |
| Problem Summary: | |
For DPS system , if global event monitor run out of "Database
Monitor Heap" memory during event monitor activation. It can
get
stuck in "Pending remote" status.
Here is the example of the "db2 list applications global show
detail"
CONNECT Auth Id
Application Name Appl. Application Id
Seq# Number of Coordinating DB
Coordinator Status Status Change
Time DB Name DB Path
Handle
Agents partition number
pid/thread------------------------------------------------------
----------------------------------------------------------------
----------
-------------------- ----------
--------------------------------------------------------------
----- ---------- ---------------- ---------------
------------------------------ --------------------------
-------- --------------------
DB2INST1
db2taskd 53 *N0.DB2.100416004033
00001 1 0
26 Connect Completed Not Collected
SAMPLE /export/home/db2inst1/db2inst1/NODE0000/SQL00001/
DB2INST1
db2wlmd 54 *N0.DB2.100416004034
00001 1 0
27 Connect Completed Not Collected
SAMPLE /export/home/db2inst1/db2inst1/NODE0000/SQL00001/
DB2INST1
db2evmg_DB2DETAILDEA 58 *N0.DB2.100416004113
00002 3 0
34 Pending remote request Not Collected
SAMPLE /export/home/db2inst1/db2inst1/NODE0000/SQL00001/
DB2INST1
db2evmg_DB2DETAILDEA 59 *N0.DB2.100416004116
00004 3 0
35 Pending remote request Not Collected
SAMPLE /export/home/db2inst1/db2inst1/NODE0000/SQL00001/
DB2INST1
db2evmg_DB2DETAILDEA 60 *N0.DB2.100416004119
00006 3 0
36 Pending remote request Not Collected
SAMPLE /export/home/db2inst1/db2inst1/NODE0000/SQL00001/ | |
| Local Fix: | |
INCREASE EVENT MONITOR HEAP. | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
With this fix, there will be ab error instead of the event monitor getting stuck in "pending remote" status state. Issue fixed in v9.7 fixpack 3 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 18.05.2010 04.10.2010 04.10.2010 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP3 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.3 |
|
| 9.7.0.3 |
|