|
Problem IC96255
|
Status: Closed |
CONNECTION HANGS ON ACR AFTER COMMUNICATION ERROR. ALTERNATE SERVER INFORMATION from the database catalog IS NOT USED. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - 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 to v10.1 fp3 *
**************************************************************** |
| 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 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
|
| Solution |
First fixed in v10.1 fp3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.09.2013
18.10.2013
18.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
