DB2 FOR LUW / DB2FORLUW / A10 - DB2

When under connection pooling, the application can get a 
connection via OCISessionGet() that is no longer active because 
of the tcpip keep alive processing which terminated a connection 
that was idle for more than the default interval (2 hours).  CLI 
does not detect this either as no indication that the connection 
has been terminated is ever given to the client at any layer. 
The only way to verify this for sure was to capture a DB2CI 
trace with TraceTimestamp=1 to see that a given connection was 
not used in over 2 hours or trace tcpip itself (not sure how to 
do this).

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4                       * 
****************************************************************

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
 

First fixed in Version 10.1 Fix Pack 4

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC97096 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

01.09.2013
21.10.2013
21.10.2013