home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC61735 Status: Closed

INVALID SETTINGS MAY BE READ FROM DB2DSDRIVER.CFG WHEN CONNECTION
IS ESTABLISHED VIA CLP

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Invalid settings may be read from db2dsdriver.cfg in case of CLP 
when a catalogued DB name and a alias name in db2dsdriver.cfg 
are same. 
 
db2 uncatalog db EC206 
db2 uncatalog node n206 
db2 catalog tcpip node n206 remote INEC006.svldev.svl.ibm.com 
server 446 ostype mvs 
db2 catalog db STLEC1 as EC206 at node n206 authentication dcs 
db2 connect to eC206 user newton using G00dMove 
 
 
<configuration> 
<DSN_Collection> 
<dsn alias="ec206" name="stlec1" 
host="LABEC27.svldev.svl.ibm.com" port="446"> 
</dsn> 
</DSN_Collection> 
<databases> 
<database name="stlec1" host="LABEC27.svldev.svl.ibm.com" 
port="446"> 
<parameter name="UserID" value="newton"/> 
<parameter name="CommProtocol" value="TCPIP"/> 
<WLB> 
<parameter name="enableWLB" value="true"/> 
</WLB> 
<ACR> 
<parameter name="enableACR" value="true"/> 
</ACR> 
</database> 
</databases> 
<parameters> 
<parameter name="param4" value="value4"/> 
</parameters> 
</configuration>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Invalid settings maybe read from db2dsdriver.cfg when a      * 
* catalogued DB and a DSN in db2dsdriver.cfg are defined using * 
* same name.                                                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v97FP1.                                           * 
****************************************************************
Local Fix:
Use different alias names in DB catalog and db2dsdriver.cfg
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Solution
v97FP1 will have the fix.
Workaround
Use different alias name in DB catalog and db2dsdriver.cfg
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.06.2009
21.12.2009
10.12.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList