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 IC88482 Status: Geschlossen

DB2 INSTANCE PANICS IN SETUPCTLMSGTARGETS WHEN TRYING TO ACTIVATE EVENT
MONITOR WRITERS.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
While trying to activate event monitor writers  when some node 
failure recoveries are being done on other partitions . The node 
failure recovery triggered the panic because we interrupted the 
subagent doing the event monitor activation with a 
SQLE_PDB_INTRPT_NODEFAIL_EVMON_SUBAGENT interrupt. This locally 
generated interrupt does not need to reply to any coordinator 
which is causing the panic. 
 
db2diag.log entries show: 
2012-10-19-22.40.49.584294-240 I638305A490        LEVEL: Severe 
PID     : 9699638              TID  : 49734       PROC : db2sysc 
66 
INSTANCE: pbdw01               NODE : 066         DB   : DBxxxx 
APPHDL  : 0-26927              APPID: 
1xx.14x.16x.1x.55951.1210200239 
AUTHID  : xxxxx 
EDUID   : 49734                EDUNAME: db2agntp (DBxxxx) 66 
FUNCTION: DB2 UDB, fast comm manager, 
sqkfChannel::SetupCtlMsgTargets, probe:10 
MESSAGE : Prog Error - Cannot multicast control on data channel 
 
--- 
Trap file shows 
<Header> 
---- 
process id: 9699638 
thread id : 49734 (0xC246) 
kthread id : 95486143 
--- 
--- 
--- 
</POFDisassembly> 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x0900000000AA37D0 pthread_kill + 0xB0 
0x090000001A538F1C sqloDumpEDU + 0x54 
0x0900000018EB2E4C sqle_panic__Fv + 0x8C 
0x0900000019D753A4 SetupCtlMsgTargets__11sqkfChannelFPUciT2 + 
0xF8 
0x090000001AA087A8 
sqlkd_snd_init__FP8SQLKD_CBiT2P18SQLZ_PDB_UNIQUE_IDPUc16SQLKF_BU 
FFER_PRIT2 + 0x23C 
0x0900000019460638 sqlkdSendReply__FP16sqlkdRqstRplyFmt + 0x6DC 
0x0900000019E89A90 
sqleSendReply__FiT1P8sqeAgentP14sqeApplicationP8SQLKD_CBP15SQLKD 
_REPLY_MSG + 0x110 
0x0900000018D6BF5C sqleReplyToSender__FP8sqeAgentPUiT2 + 0x2A0 
0x0900000018F27C98 SubAgentPostProcessing__8sqeAgentFPiPUiT2 + 
0x694 
0x0900000018D70600 sqleProcessSubRequest__FP8sqeAgent + 0x14B0 
0x0900000019945CDC RunEDU__8sqeAgentFv + 0x2FC 
0x090000001CD06C18 EDUDriver__9sqzEDUObjFv + 0xDC 
0x090000001CD23338 sqloEDUEntry + 0x270 
</StackTrace>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 8                        * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First Fixed in Version 9.7 Fix Pack 8
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC91285 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.11.2012
01.04.2013
01.04.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP8
Problem behoben lt. FixList in der Version
9.7.0.8 FixList