|
Problem IC86972
|
Status: Closed |
CONNECTION HANGS ON ACR AFTER COMMUNICATION ERROR. ALTERNATE SERVER INFORMATION from the database catalog IS NOT USED. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* upgrade *
**************************************************************** |
| Local Fix: |
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> |
| available fix packs: |
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 |
first fixed in v9.7fp8 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC96255
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.10.2012
24.09.2013
24.09.2013 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.8
|
 |
