IBM Support

IC77832: WHEN INVALID SERVERS(IN ALTERNATESERVERLIST) ARE GIVEN IN DB2DSD RIVER.CFG, IT TAKES VERY LONG FOR REPLY WITH SQLRELOADCONFIG.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error 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.
    

Local fix

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.                                  *
    ****************************************************************
    

Problem conclusion

  • Fixed in v97fp5.
    Delay will be same as specified through ConnectionTimeout or
    tcpipConnectTimeout.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC77832

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-07-29

  • Closed date

    2011-12-08

  • Last modified date

    2011-12-08

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC77832

Modified date: 08 December 2011