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

DB2 INSTANCE COULD HANG WHEN MESSAGE QUEUE RESOURCES ARE SCARCE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
In certain rare scenarios it is possible for a DB2 instance on 
UNIX/Linux to hang when the system runs out of message queue 
resources.  This type of hang is mostly commonly encountered 
while executing parallel loads.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 on UNIX/Linux                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Sending messages on system message queues may block forever  * 
* when resources are scarce.  Stack traces will show threads   * 
* blocked in msgsnd.                                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Retry the operation.  Increase system message queue          * 
* resources in the kernel if possible.  Upgrade to DB2 v9.7    * 
* fixpack 5.                                                   * 
****************************************************************
Local-Fix:
Retry the operation with less parallelism.  If possible, 
increase the message queue resources configured in the kernel.
Lösung
Allow non-blocking message sends and gracefully handle cases 
when they fail due to limited resources.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.10.2011
08.12.2011
08.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.
Problem behoben lt. FixList in der Version