|
Problem IC85879
|
Status: Closed |
CAN NOT READ PROPERTIES E.G ACR FROM DB2DSDRIVER.CFG |
| product: |
DB2 CONNECT / DB2CONNCT / A10 - DB2 |
| Problem description: |
If we define a alternate group e.g DSND1 and then define DSND1
then ACR properties of DSND1 is not read for below
db2dsdriver.cfg file for db2cli validate command:
<database name="DSNI1" host="9.30.178.50" port="52100">
<wlb>
<parameter name="enableWLB" value="true"/>
<parameter name="maxTransports" value="25"/>
</wlb>
<acr>
<parameter name="enableAcr" value="true"/>
<parameter name="enableSeamlessAcr" value="true"/>
<alternategroup>
<parameter name="enableAlternateGroupSeamlessACR"
value="true"/>
<database name="DSND1" host="9.30.179.1" port="52600"/>
</alternategroup>
</acr>
</database>
<database name="DSND1" host="9.30.179.1" port="52600">
<wlb>
<parameter name="enableWLB" value="true"/>
<parameter name="maxTransports" value="25"/>
</wlb>
<acr>
<parameter name="enableAcr" value="true"/>
<parameter name="enableSeamlessAcr" value="true"/>
</acr>
</database>
db2dsdriver.cfg Validation :
----------------------------------------------------------------
-----------
[ DB2DSDRIVER_CFG_PATH env var : unset ]
[ db2dsdriver.cfg Path : C:\Documents and Settings\All
Users\Applicati
on Data\IBM\DB2\IBMDBCL1\cfg\db2dsdriver.cfg ]
----------------------------------------------------------------
-----------
[ List of keywords used for DSN : dsnd1 ]
Keywords Valid For Value
-------------------------------------------------------
DATABASE CLI,.NET,ESQL DSND1
HOSTNAME CLI,.NET,ESQL 9.30.179.1
PORT CLI,.NET,ESQL 52600
AUTHENTICATION CLI,.NET Server_Encrypt
COMMPROTOCOL CLI TCPIP
----------------------------------------------------------------
-----------
The validation completed |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users using db2cli validate tool *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V101 FP1 or later releases *
**************************************************************** |
| Local Fix: |
In the db2dsdriver.cfg, put all the <database> sections before
including the same <database> section in the <alternategroup>
sections |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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 |
V101 FP1 fixes the issue |
| Workaround |
In the db2dsdriver.cfg, put all the <database> sections before
including the same <database> section in the <alternategroup>
sections |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.08.2012
31.10.2012
31.10.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
