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

DATABASE MAY HANG DUE TO SMALL TIMING HOLE WHEN TERMINATING AGENT SIGNALS
LOGGER TO FLUSH THE TRANSACTION BUFFER

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
There is a small timing hole that can cause a database hang. 
When a terminating agent may need to have the transaction log 
buffer flushed, it posts a message to the db2loggr agent.  In 
rare cases, if the db2loggr is responding to other posts at the 
same time, the post from the terminating agent may get lost. 
 
 
The db2agent would have the following stack, where it is waiting 
for a response from the db2loggr thread.  This agent would be 
holding the database latch during this time, which will cause 
other agents waiting for the latch to wait. 
 
sqloWaitEDUWaitPost 
sqlpgPostLoggrWithoutLatching 
sqlpterm 
sqeLocalDatabase::CleanDB 
sqeLocalDatabase::TermDbConnect 
sqeApplication::AppStopUsing 
sqlesrspWrp 
sqleUCagentConnectReset 
sqljsCleanup 
sqljsDrdaAsInnerDriver 
sqljsDrdaAsDriver 
sqeAgent6RunEDU 
sqlzRunEDU 
 
 
 
The db2loggr thread, not seeing a waiting action would then go 
to sleep waiting for more work: 
 
sqloWaitEDUWaitPost 
sqlpgasnPcj 
sqloEDUEntry
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 7 or higher              * 
****************************************************************
Local-Fix:
None, though the chance to hit the timing hole is small.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
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
Problem first fixed in DB2 Version 9.7 Fix Pack 7
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
11.01.2012
31.10.2012
31.10.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP7
Problem behoben lt. FixList in der Version
9.7.0.7 FixList