|
Problem IC87861
|
Status: Closed |
SOCKET TIMEOUT MESSAGES IN DB2DIAG.LOG FILE ARE DOWNGRADED TO INFORMATIONAL MESSAGES. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Socket timeout messages are dumped as informational message to
notify user that connection is lost because of timeout.
The messages previously logged as severe error as shown below:
2012-04-11-10.03.24.171000-240 I14854F403 LEVEL: Error
PID : 3216 TID : 3272 PROC :
DB2Test.exe
INSTANCE: NODE : 000
APPID : 192.168.1.10.61129.120411140318
EDUID : 3272
FUNCTION: DB2 UDB, common communication, sqlcctcpconnr,
probe:110
MESSAGE : DIA3202C The TCP/IP call "selectForConnectTimeout"
returned an
errno="0".
2012-04-11-10.03.24.171000-240 I15259F479 LEVEL: Severe
PID : 3216 TID : 3272 PROC :
DB2Test.exe
INSTANCE: NODE : 000
APPID : 192.168.1.10.61129.120411140318
EDUID : 3272
FUNCTION: DB2 UDB, DRDA Communication Manager, sqljcCommConnect,
probe:10
MESSAGE : ZRC=0x8136001A=-2127167462=SQLJC_ERROR_TIMEOUT
"CONNECTION TIMED OUT"
DATA #1 : String, 11 bytes
CCI Error:
DATA #2 : unsigned integer, 8 bytes
162
After the APAR fix timeout message is logged as LEVEL Info. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v10.1.2. or higher fixpack. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem Fixed in DB2 Version 10.1.2. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.11.2012
02.01.2013
02.01.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
