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

CATALOG NODE FAILURE CAN LEAD TO SYSTEM APPICATIONS NOT TERMINATING AND
CAUSE SQL1229N ON NON-CATALOG NODES.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
A catalog node failure can lead to a timing issue on non-catalog 
nodes where certain system applications are concurrently being 
interrupted by a node failure interrupt and a force interrupt 
causing the force interrupt to be lost. If the catalog node 
failure interrupt happens and the agent does not process it 
completely before the force interrupt comes in, (due to the last 
user connection on a db forcing off all applications) the force 
interrupt will be lost and the system application will return to 
its waitpost. The last user connection will be waiting in 
TermDbConnect on lastSysApplOut forever. Any other applications 
attempting to connect to this db will get -1229. 
 
The stack of the last user connection will be in this state: 
 
thread_wait 
sqloWaitEDUWaitPost 
TermDbConnect 
AppStopUsing 
sqlesrspWrp 
sqleUCagentConnectReset 
sqljsCleanup 
sqljsDrdaAsInnerDriver 
sqljsDrdaAsDriver 
RunEDU 
EDUDriver 
sqloEDUEntry 
 
And the fast writer system application will be in this state: 
 
thread_wait 
sqloWaitEDUWaitPost 
executeFastWriter 
sqleIndCoordProcessRequest 
RunEDU 
EDUDriver 
sqloEDUEntry
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1                       * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 Version 10.1 Fix Pack 1
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.06.2012
13.11.2012
13.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList