|
Problem IC77832
|
Status: Closed |
WHEN INVALID SERVERS(IN ALTERNATESERVERLIST) ARE GIVEN IN DB2DSD RIVER.CFG, IT TAKES VERY LONG FOR REPLY WITH SQLRELOADCONFIG. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Steps To Reproduce
1. Have a valid db2dsriver.cfg. For e.g.
<configuration>
<dsncollection>
<dsn alias="alias1" name="DB1" host="xyz.com"
port="9999"/>
</dsncollection>
<databases>
<database name="DB1" host="xyz.com" port="9999">
<acr>
<parameter name="enableACR" value="true"/>
<parameter name="enableSeamlessACR"
value="true"/>
<alternateserverlist>
<server name="S1" hostname="xyz.com"
port="9999"/>
<server name="S2" hostname="xyz1.com"
port="9999"/>
</alternateserverlist>
<affinitylist>
<list name="list1" serverorder="S1,S2"/>
</affinitylist>
<clientaffinitydefined>
<client name="client1" hostname="host.com"
listname="list1"/>
</clientaffinitydefined>
</acr>
</database>
</databases>
<parameters>
<parameter name="ConnectionTimeout" value="10"/>
</parameters>
</configuration>
2. Connect to xyz.com SQLDRIVERCONNECT
Connection is a success
3. Change the contents of the db2dsriver.cfg file, the S1 and S2
hostnames are now invalid.
<configuration>
<dsncollection>
<dsn alias="alias1" name="DB1" host="xyz.com"
port="9999"/>
</dsncollection>
<databases>
<database name="DB1" host="xyz.com" port="9999">
<acr>
<parameter name="enableACR" value="true"/>
<parameter name="enableSeamlessACR"
value="true"/>
<alternateserverlist>
<server name="S1" hostname="9.122.122.22"
port="9999"/>
<server name="S2" hostname="9.122.122.23"
port="9999"/>
</alternateserverlist>
<affinitylist>
<list name="list1" serverorder="S1,S2"/>
</affinitylist>
<clientaffinitydefined>
<client name="client1" hostname="host.com"
listname="list1"/>
</clientaffinitydefined>
</acr>
</database>
</databases>
<parameters>
<parameter name="ConnectionTimeout" value="10"/>
</parameters>
</configuration>
4. Reload using SQLReloadConfig with configproperty
DSD_ACR_AFFINITY
Since the server's S1 and S2 are wrong we get following error
message in diagnostic string, which is expected.
DiagInfoString: IBM DB2 [CLI Driver] <DB1>:<xyz.com>:<999> -
None of the servers, specified under <alternateserverlist>
section, are reachable.
The issue is, it takes around 4-6 minutes for this error. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* WHEN INVALID SERVERS(IN ALTERNATESERVERLIST) ARE GIVEN IN *
* DB2DSD *
* RIVER.CFG, IT TAKES VERY LONG FOR REPLY WITH *
* SQLRELOADCONFIG. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v97fp5 or later. *
**************************************************************** |
| 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 |
Fixed in v97fp5.
Delay will be same as specified through ConnectionTimeout or
tcpipConnectTimeout. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.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
|
 |
