|
Problem IT09874
|
Status: Closed |
COORDINATOR AGENT MAY HANG IN PENDING REMOTE REQUEST |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
In a DPF environment, an application may hang with the agent
stuck in "Pending Remote Request" state on the coordinator node.
This can happen if the coordinator node's start time was later
than the other nodes'.
The coordinator agent stack shows that it is stuck in
sqkfChannel::ReceiveBuffer. It is waiting for a reply from
another node, and that node may have an error in the db2diag.log
similar to the one below:
2015-06-19-04.13.32.124062-240 I12469252A432 LEVEL: Error
PID : 16056538 TID : 3085 PROC :
db2sysc 41
INSTANCE: db2inst1 NODE : 041
HOSTNAME: appad05a0021
EDUID : 3085 EDUNAME: db2pdbc 41
FUNCTION: DB2 UDB, fast comm manager,
sqkfFastCommManager::DeliverBufferToTargetChannel, probe:1255
DATA #1 : <preformatted>
CommSession timestamp = 1749920
App timestamp = 1034042
Note that if "CommSession timestamp" is greater than "App
timestamp", then this APAR may apply. In the above example, the
coordinator agent was stuck waiting for a reply from node 41 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to DB2 v9.7 Fix Pack 11 *
**************************************************************** |
| Local Fix: |
N/A |
| Solution |
Problem first fixed in DB2 v9.7 Fix Pack 11 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.07.2015
19.10.2015
19.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
|
 |
