DB2 - Problem description
| Problem IC66500 | Status: Closed |
THE DIA3208E ERROR IS LOGGED IN DB2DIAG.LOG WHEN DB2STOP IS CALLED WHILE THE INSTANCE IS STOPED SUCCESSFULLY | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
The DIA3208E error is logged in db2diag.log when multiple
communication managers ( tcpcm ) are working and db2stop is
called while the instance is stoped successfully.
The following db2diag.log entry at db2stop is a eye-catcher of
this issue.
$ db2stop
2008-10-07 09:35:47 0 0 SQL1064N DB2STOP processing was
successful.
DB2STOP processing was successful.
$ db2diag
2008-10-07-09.35.45.429886+540 I46390A429 LEVEL: Error
PID : 729240 TID : 1800 PROC : db2sysc
0
INSTANCE: db2v9ins NODE : 000
EDUID : 1800 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 "6". Errno was "9". | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * User using database with multiple connections * **************************************************************** * PROBLEM DESCRIPTION: * * The DIA3208E error logs are recorded on * * multiplecommunication managers ( tcpcm ) working when * * db2stop iscalled even if the instance is stoped * * successfully. * **************************************************************** * RECOMMENDATION: * * Upgrade to db2 Version 9.7 FixPak 2 * **************************************************************** | |
| Local Fix: | |
db2set DB2TCPCONNMGRS=1 | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
| Solution | |
Problem was first fixed in Version 9.7 FixPak 2 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.02.2010 25.05.2010 25.05.2010 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7. | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.2 |
|