Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC63765 Status: Closed

DUPLICATE CLOSING SOCKET DURING TERMINATING TCPIP CONNECTION
MANAGER(DB2TCPCM).

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
If db2 instance has more than one db2tcpcm processes, when they 
are requested to be terminated while instance stopping, they 
will close same socket simultaneously. As a result, only one 
db2tcpcm can close socket without error, while other db2tcpcm 
processes will received an error from system call. Then, those 
failed db2tcpcm processes will report a DIA3208E error in 
db2diag.log as follow. 
 
2010-01-01-01.01.01.111111+000 I142076E431         LEVEL: Error 
PID     : 1111                 TID  : 1111         PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 19                   EDUNAME: db2tcpcm 0 
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, 
probe:155 
MESSAGE : DIA3208E Error encountered in TCP/IP protocol support. 
TCP/IP 
          function "close". Socket was "3". Errno was "9". 
 
This APAR is opened for erasing this error message to avoid 
unnecessary concern about this non-critical message.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL.                                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If db2 instance has more than one db2tcpcm processes,        * 
* whentheyare requested to be terminated while instance        * 
* stopping, theywill close same socket simultaneously. As a    * 
* result, only onedb2tcpcm can close socket without error,     * 
* while otherdb2tcpcmprocesses will received an error from     * 
* system call. Then,thosefailed db2tcpcm processes will report * 
* a DIA3208E error indb2diag.log as                            * 
* follow.2010-01-01-01.01.01.111111+000 I142076E431            * 
* LEVEL:ErrorPID    : 1111                TID  : 1111          * 
* PROC :db2sysc 0INSTANCE: db2inst1            NODE : 000EDUID * 
*  : 19                  EDUNAME: db2tcpcm 0FUNCTION: DB2 UDB, * 
* common communication,sqlcctcpconnmgr_child,probe:155MESSAGE  * 
* : DIA3208E Error encountered in TCP/IP                       * 
* protocolsupport.TCP/IPfunction "close". Socket was "3".      * 
* Errno was "9".This APAR is opened for erasing this error     * 
* message to avoidunnecessary concern about this non-critical  * 
* message.                                                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to version 9.5 fix pack 6 or later.                   * 
****************************************************************
Local Fix:
set db2 register variable DB2TCPCONNMGRS to 1, then recycle the 
instance. But, please note that DB2TCPCONNMGRS=1 will degrade 
connecting performance. Please refer to corresponding topics 
about "DB2TCPCONNMGRS" in db2 information center.
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
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
This problem is first fixed in version 9.5 fix pack 6.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC63766 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.10.2009
25.05.2010
25.05.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)
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.