DB2 FOR LUW / DB2FORLUW / 970 - DB2

ACR is not started after hitting communication error. ACR does 
not look at alternate server information in directory. The 
defect was introduced in v9.7.5. 
 
The problem can happen for connections established 
from non-JDBC clients (including CLP) and from 
non-JDBC drivers.

**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade                                                      * 
****************************************************************

To work-around the issue explicitly enable ACR ( enableACR) in 
db2dsdriver.cfg, set keepAliveTimeout and tcpipConnectTimeout. 
See the example appended below. 
 
Example to enableACR in db2dsdriver.cfg 
<configuration> 
   <DSN_Collection> 
      <dsn alias="sample" name="sample" host="samplehost" 
port="xxxxxx"/> 
      </dsn> 
   </DSN_Collection> 
   <databases> 
      <database name="sample" host="samplehost" port="xxxxxx"> 
         <ACR> 
            <parameter name="enableACR" value="true"/> 
         </ACR> 
         <parameter name="keepAliveTimeout" value="15"/> 
         <parameter name="TcpipConnectTimeout" value="2"/> 
      </database> 
  </databases> 
</configuration>

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
 

first fixed in v9.7fp8

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC96255 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

03.10.2012
24.09.2013
24.09.2013

9.7.FP8