home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT09874 Status: Geschlossen

COORDINATOR AGENT MAY HANG IN PENDING REMOTE REQUEST

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 v9.7 Fix Pack 11                               * 
****************************************************************
Local-Fix:
N/A
Lösung
Problem first fixed in DB2 v9.7 Fix Pack 11
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
06.07.2015
19.10.2015
19.10.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP11
Problem behoben lt. FixList in der Version
9.7.0.11 FixList