home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC79197 Status: Closed

DB2 INSTANCE COULD HANG WHEN MESSAGE QUEUE RESOURCES ARE SCARCE

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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.5    * 
* fixpack 9.                                                   * 
****************************************************************
Local Fix:
Retry the operation with less parallelism.  If possible, 
increase the message queue resources configured in the kernel.
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Allow non-blocking message sends and gracefully handle cases 
when they fail due to limited resources.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC79211 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.10.2011
12.03.2012
12.03.2012
Problem solved at the following versions (IBM BugInfos)
9.0.,
9.5.
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList