Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC87861 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.1.2. or higher fixpack.                       * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

Lösung
Problem  Fixed in DB2 Version 10.1.2.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.11.2012
02.01.2013
02.01.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.2 FixList
10.5.0.2 FixList