|
Problem IC80035
|
Status: Closed |
AFTER COMMUNICATION ERROR ( OR CONNECTION TIMEOUT ERROR), TRANSACTION IS FAILING WITH SQLCODE 30081 |
| product: |
DB2 CONNECT / DB2CONNCT / 970 - DB2 |
| Problem description: |
.NET Driver fails to do Automatic Client Reroute (ACR).
Tranasactions are failing with sql30081 rc=10060 timeout.
Some connections fail and others result in the db2diag.log
messages.
This issue is only applicable if:
enableWLB=true
Connections appear to be working but db2diag.log file shows:
2011-07-11-14.49.48.408000-240 I61457F403 LEVEL: Error
PID : 4712 TID : 3260 PROC :
DB2Test.exe
INSTANCE: NODE : 000
APPID : 10.40.28.92.65080.110711184401
EDUID : 3260
FUNCTION: DB2 UDB, common communication, sqlcctcpconnr,
probe:110
MESSAGE : DIA3202C The TCP/IP call "selectForConnectTimeout"
returned an
errno="0".
2011-07-11-14.49.48.408000-240 I61862F479 LEVEL: Severe
PID : 4712 TID : 3260 PROC :
DB2Test.exe
INSTANCE: NODE : 000
APPID : 10.40.28.92.65080.110711184401
EDUID : 3260
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
Some transactions failing with the sql30081 rc=10060
The errors in the db2diag.log file are Severe indicating the
Connection failure. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users connecting to DB2 for z/OS *
****************************************************************
* PROBLEM DESCRIPTION: *
* .NET Driver fails to do Automatic Client Reroute (ACR). *
* Tranasactions are failing with sql30081 rc=10060 timeout. *
* Some connections fail and others result in the db2diag.log *
* messages. *
* *
* This issue is only applicable if: *
* enableWLB=true *
* *
* Connections appear to be working but db2diag.log file shows: *
* *
* 2011-07-11-14.49.48.408000-240 I61457F403 LEVEL: *
* Error *
* PID : 4712 TID : 3260 PROC : *
* DB2Test.exe *
* INSTANCE: NODE : 000 APPID : *
* 10.40.28.92.65080.110711184401 *
* EDUID : 3260 FUNCTION: DB2 UDB, common communication, *
* sqlcctcpconnr, probe:110 *
* MESSAGE : DIA3202C The TCP/IP call "selectForConnectTimeout" *
* returned an errno="0". *
* *
* 2011-07-11-14.49.48.408000-240 I61862F479 LEVEL: *
* Severe *
* PID : 4712 TID : 3260 PROC : *
* DB2Test.exe *
* INSTANCE: NODE : 000 APPID : *
* 10.40.28.92.65080.110711184401 *
* EDUID : 3260 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 *
* *
* Some transactions fail with the sql30081 rc=10060. *
* *
* The errors in the db2diag.log file are Severe, indicating *
* the Connection failure. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB Version 9.7 Fix Pack 6 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
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 was first fixed in DB2 UDB Version 9.7 Fix Pack 6. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.11.2011
11.06.2012
11.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
