DB2 - Problembeschreibung
Problem IC97822 | Status: Geschlossen |
DB2 MAY TRAP IN sqleCleanupFedDaemonAnchor DURING MULTIPLE LOGICAL NODES STARTUP | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
This timing related trap happens only on an MLN DPF setup where the different nodes start up at different times, usually when one node starts much later than the rest. The node where the trap occurs is in the process of starting up and has not reached the initialization of the federated fmp daemon anchor yet. While on another MLN the startup has completed including starting up global event monitors. The event monitor can dispatch a request to the trapping MLN where a subagent is deployed to service the request. This subagent can be interrupted at any time and drive an application termination. Part of the application termination involves clean up of the federated daemon anchor. However, if the federated daemon anchor hasn't been initialized yet this can lead to the trap. The stack trace of the crashed subagent looks like the following: sqleCleanupFedDaemonAnchor__Fv + 0xD0 sqleFedFMPManagerFv + 0x150 TermApplication__14sqeApplicationFv + 0x5C DestroyAppl__14sqeAppServicesFP14sqeApplication + 0x49C sqleProcessSubRequest__FP8sqeAgent + 0x298 RunEDU__8sqeAgentFv + 0x308 EDUDriver__9sqzEDUObjFv + 0x78 sqloEDUEntry + 0x4 In the db2diag.log, the trapping node (i.e. node 4) initiates db2start much later than node 0 where the subagent request was dispatched. 2013-07-11-02.01.54.471940+480 E217431820A314 LEVEL: Event PID : 234888 TID : 1 PROC : db2star2 INSTANCE: db2inst2 NODE : 000 EDUID : 1 FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911 MESSAGE : ADM7513W Database manager has started. START : DB2 DBM ... 2013-07-11-02.02.12.276740+480 E217723221A314 LEVEL: Event PID : 135176 TID : 1 PROC : db2star2 INSTANCE: db2inst2 NODE : 004 EDUID : 1 FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911 MESSAGE : ADM7513W Database manager has started. START : DB2 DBM 2013-07-11-02.02.12.329472+480 I217724005A531 LEVEL: Error PID : 415072 TID : 2057 PROC : db2sysc 4 INSTANCE: db2inst2 NODE : 004 APPHDL : 0-69 APPID: *N0.DB2.130710180215 AUTHID : DB2INST2 EDUID : 2057 EDUNAME: db2agent (idle) 4 FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, probe:1 MESSAGE : Error in agent servicing application with coor_node: DATA #1 : Hexdump, 2 bytes 0x070000000E009330 : 0000 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All platforms * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.1 fix pack 5 * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
The fix will be included in DB2 version 10.1 fix pack 5. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 21.11.2013 06.10.2014 06.10.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.4 | |
10.1.0.5 |