|
Problem IC84133
|
Status: Closed |
DB2.NET MAY NOT FIND A PARAMETER IN THE DB2DSDRIVER.CFG FOR INSTANCE BASED CLIENTS. |
| product: |
DB2 CONNECT / DB2CONNCT / A10 - DB2 |
| Problem description: |
When using the db2dsdriver.cfg file on instance based clients
(eg, Data Server Client) instead of the Data Server Driver, it
is possible that a parameter in the db2dsdriver.cfg file does
not get picked up by a DB2 .NET application.
For example, assume the following db2dsdriver.cfg file exists:
<configuration>
<dsncollection>
<dsn alias="DBDT#RP" name="MYDB" host="myhost" port="447">
<parameter name="CurrentSchema" value="MYSCHEM1"/>
</dsn>
<dsn alias="DBNT#RP" name="MYDB" host="myhost" port="447">
<parameter name="CurrentSchema" value="MYSCHEM2"/>
</dsn>
<dsn alias="DBPT#RP" name="MYDB" host="myhost" port="447">
<parameter name="CurrentSchema" value="MYSCHEM3"/>
</dsn>
<dsn alias="DBBP#RP" name="MYDB" host="myhost" port="447">
<parameter name="CurrentSchema" value="MYSCHEM4"/>
</dsn>
</dsncollection>
</configuration>
In this specific case it is possible that the DBDT#RP data
source would not find its CurrentSchema, yet all the others
would.
The problem stems from having a DCS directory and having the
'name' field in the db2dsdriver.cfg file not properly finding
its DCS name in the DCS directory when it should. Since a DCS
directory has to be involved this means that this APAR will only
affect clients connecting to DCS servers such as DB2 for z/OS or
DB2 for iSeries. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v10.1, Fixpak 1 *
**************************************************************** |
| Local Fix: |
Uncataloging the DCS directory or using a Data Server Driver
will resolve this problem. Another workaround would be to
modify the 'name' field in the db2dsdriver.cfg file to match the
local database name in the DCS directory as opposed to the
target database name. |
| 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 |
First fixed in DB2 v10.1, Fixpak 1 |
| Workaround |
see Local Fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.06.2012
05.11.2012
05.11.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
|
|
