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 IC75114 Status: Closed

INSTANCE MAY CRASH WHEN A NEW DISPATCHER IS REQUIRED.

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
When using connection concentrator, if more dispatchers are 
required than originally calculated to handle the concurrent 
connections, the instance can crash. 
 
 
The following message can be seen in db2diag.log before the 
crash : 
 
2011-03-09-18.10.51.966610-300 I28977A644        LEVEL: Severe 
PID    : 13402256            TID  : 1          PROC : 
db2agent (DB8) 
INSTANCE: db2inst1            NODE : 000 
APPHDL  : 0-452                APPID: 
*LOCAL.db2inst1.110309231710 
AUTHID  : DB2INST1 
FUNCTION: DB2 UDB, base sys utilities, 
sqeDomainSocketManager::GetDispatcherSoc, 
probe:10 
DATA #1 : <preformatted> 
maxLogicalConnections = 610 
maxDescriptors = 32767 
numdb = 1 
SQLE_CALC_NUM_DISPATCHER_PAIRS = 2 
SQLE_DISPATCHER_NUM_CONNS = 500 
SQLE_NUM_FREE_CONN_DESC = 32595 
SQLE_APP_GROUP_NUM_DESC = 7 
SQLE_NUM_RESERVED_DESC = 172 
FD_SETSIZE = 32767 
SQLE_MAXAGENTS_OVERFLOW = 50 
 
The calculated number of dispatchers is given by 
SQLE_CALC_NUM_DISPATCHER_PAIRS.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.1 FP11                                      * 
****************************************************************
Local Fix:
n/a
available fix packs:
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
The problem is first fixed in DB2 9.1 FP11
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.03.2011
19.01.2012
19.01.2012
Problem solved at the following versions (IBM BugInfos)
9.1.FP11
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.11 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.