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 IC77471 Status: Closed

MULTIPLE CONNECTION FAILURES WHEN ENABLEWLB=TRUE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When 'enableWLB' is set to true, for a new logical connection, 
after successful communication 
layer initialization, client fails to send the request and an 
application / client receives multiple -30081 errors with error 
"selectForRecvTimeout". If enableWLB=false, it all works fine, 
no errors. 
 
- db2diag.log shows : 
 
'ZRC=0x8136001A=-2127167462=SQLJC_ERROR_TIMEOUT "CONNECTION 
TIMED OUT"' errors. 
 
- The zDB2 member reports: 
 
DSNL511I  )TB3C DSNLIENO TCP/IP CONVERSATION FAILED  126 
          TO LOCATION :: <IP Address> 
          IPADDR=::<IP Address>  PORT= <Port Number> 
 
          SOCKET=RECV RETURN CODE=1121 REASON CODE=00000000 
 
- CLI traces : 
 
SQLFreeHandle( fHandleType=SQL_HANDLE_DBC, hHandle=0:1 ) 
    ---> Time elapsed - +2.200000E-005 seconds 
( Unretrieved error message="[IBM][CLI Driver] CLI0106E 
Connection is closed. SQLSTATE=08003" ) 
( Number of allocations left before we freed the Pool=1 )
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users on DB2 V9.7 FixPack 4 or below                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When 'enableWLB' is set to true, for a new logical           * 
* connection,                                                  * 
* after successful communication                               * 
*                                                              * 
* layer initialization, client fails to send the request and   * 
* an                                                           * 
* application / client receives multiple -30081 errors with    * 
* error                                                        * 
* "selectForRecvTimeout". If enableWLB=false, it all works     * 
* fine,                                                        * 
* no errors.                                                   * 
*                                                              * 
*                                                              * 
*                                                              * 
* - db2diag.log shows :                                        * 
*                                                              * 
*                                                              * 
*                                                              * 
* 'ZRC=0x8136001A=-2127167462=SQLJC_ERROR_TIMEOUT "CONNECTION  * 
*                                                              * 
* TIMED OUT"' errors.                                          * 
*                                                              * 
*                                                              * 
*                                                              * 
* - The zDB2 member reports:                                   * 
*                                                              * 
*                                                              * 
*                                                              * 
* DSNL511I  )TB3C DSNLIENO TCP/IP CONVERSATION FAILED  126     * 
*                                                              * 
*           TO LOCATION :: <IP Address>                        * 
*                                                              * 
*           IPADDR=::<IP Address>  PORT= <Port Number>         * 
*                                                              * 
*                                                              * 
*                                                              * 
*           SOCKET=RECV RETURN CODE=1121 REASON CODE=00000000  * 
*                                                              * 
*                                                              * 
*                                                              * 
* - CLI traces :                                               * 
*                                                              * 
*                                                              * 
*                                                              * 
* SQLFreeHandle( fHandleType=SQL_HANDLE_DBC, hHandle=0:1 )     * 
*                                                              * 
*     ---> Time elapsed - +2.200000E-005 seconds               * 
*                                                              * 
* ( Unretrieved error message="[IBM][CLI Driver] CLI0106E      * 
*                                                              * 
* Connection is closed. SQLSTATE=08003" )                      * 
*                                                              * 
* ( Number of allocations left before we freed the Pool=1 )    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 FixPack 5 or higher.                     * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 first fixed in DB2 V9.7 FixPack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.07.2011
08.12.2011
08.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList