home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC82813 Status: Closed

SOCKET TIMEOUT MESSAGES IN DB2DIAG.LOG FILE ARE DOWNGRADED TO INFORMATIONAL
MESSAGES.

product:
DB2 FOR LUW / DB2FORLUW / 970 - 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 DB2 9.7 FP7 or subsequent fix pack.               * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem First Fixed in DB2 Version 9.7 Fix Pack 7
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC87861 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.04.2012
25.10.2012
25.10.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP7
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.7 FixList