DB2 FOR LUW / DB2FORLUW / 910 - DB2

The instance may crash after using connection concentrator. The 
affected platforms are HP and Linux.  If you encounter this 
problem, the following db2diag.log messages will appear, and the 
instance will go down. 
 
The key message to watch out for is the errno at the probe 15 of 
sqeDomainSocketPair::WriteConn.  If the errno is 0xB (11), then 
you have encountered this problem. 
 
2011-03-21-09.05.02.438346+540 I4253A417          LEVEL: Severe 
PID     : 1190                 TID  : 1           PROC : 
db2agent (SAMPLE) 
INSTANCE: DB2INST1              NODE : 000 
APPID   : 111.222.333.444.37043.110319210800 
AUTHID  : DB2USER 
FUNCTION: DB2 UDB, base sys utilities, 
sqeDomainSocketPair,WriteConn, probe:10 
RETCODE : ZRC=0x80050158=-2147155624=SQLE_RC_SYSTEM_ERR 
          "Unexpected system error." 
 
2011-03-21-09.05.02.438788+540 I4671A439          LEVEL: Severe 
PID     : 1190                 TID  : 1           PROC : 
db2agent (SAMPLE) 
INSTANCE: DB2INST1              NODE : 000 
APPID   : 111.222.333.444.37043.110319210800 
AUTHID  : DB2USER 
FUNCTION: DB2 UDB, base sys utilities, 
sqeDomainSocketPair::WriteConn, probe:15 
MESSAGE : Errno = 
DATA #1 : Hexdump, 4 bytes 
0x9FFFFFFFFFFF8A54 : 0000 000B 
 
2011-03-21-09.05.02.439065+540 I5111A447          LEVEL: Severe 
PID     : 1190                TID  : 1           PROC : db2agent 
(SAMPLE) 
INSTANCE: DB2INST1              NODE : 000 
APPID   : 192.168.0.206.37043.110319210800 
AUTHID  : DB2USER 
FUNCTION: DB2 UDB, base sys utilities, 
sqeConnQueueAgentEndPoint::EnqueueConn, probe:10 
MESSAGE : Errno = 
DATA #1 : Hexdump, 4 bytes 
0x9FFFFFFFFFFF8B10 : 0000 0009 
 
<snipped...> 
 
2011-03-21-09.05.02.612298+540 I11776A437         LEVEL: Severe 
PID     : 1190                 TID  : 1           PROC : 
db2agent (SAMPLE) 
INSTANCE: DB2INST1              NODE : 000 
APPID   : 111.222.333.444.37043.110319210800 
AUTHID  : DB2USER 
FUNCTION: DB2 UDB, base sys utilities, sqle_panic, probe:10 
MESSAGE : sqle_panic: Panic/sleep = 
 
 
The following is the sack of panickng agent. 
 
(5)  0xc000000000429350 _kill + 0x30 [/usr/lib/hpux64/libc.so.1 
(6)  0xc000000016f5bea0 sqloDumpEDU + 0x40 [/TOOLS/NPPDDB2/lib6 
(7)  0xc00000001685cc60 _Z10sqle_panicv + 0xe0 [/TOOLS/NPPDDB2/ 
(8)  0xc0000000169574d0 _ZN25sqeConnQueueAgentEndPoint11Enqueue 
ConnEP19sqle_coordinator_cb + 0x1f0 [/TOOLS/NPPDDB2/lib64/libdb 
(9)  0xc00000001694ece0 _ZN17sqeConnDispatcher20XferConnToDispa 
tcherEP19sqle_coordinator_cb + 0x140 [/TOOLS/NPPDDB2/lib64/libd 
(10) 0xc00000001693c340 _ZN15sqeConcentrator22XferConnToConcent 
ratorEP19sqle_coordinator_cb + 0x100 [/TOOLS/NPPDDB2/lib64/libd

**************************************************************** 
* USERS AFFECTED:                                              * 
* Version 91 on HPUX and Linux with concentrator enabled.      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2 v91 may panic leading to a crash with connection         * 
* concentrator turned on for Linux and HP platforms.           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to version v91fp11.                                  * 
****************************************************************

If you encounter this problem, disable the connection 
concentrator until the fix is installed.

DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
 DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows
 

db2 version 91 fixpack 11 includes the fix for this issue.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

22.03.2011
20.12.2011
20.12.2011

9.1.FP11