|
Problem IC95839
|
Status: Closed |
EXEC SQL SET CONNECTION FAILED WITH SQL0843N |
| product: |
DB2 DATA SRVR D / DB2DSDRVR / A50 - DB2 |
| Problem description: |
The SET CONNECTION, sql statement may fail with SQL0843N
when the connection is made from IBM DS Driver Client and the
following conditions are met.
The database alias specified to SET CONNECTION statement is
defined in db2dsdriver.cfg.
And the values to database alias (dsn alias) and the data base
name (name) are different.
In the following example of db2dsdriver.cfg, two data source
names, PSAMPLE and SAMPLE1 are defined.
For the data source, PSAMPLE, this issue may occur because the
character strings, "PSAMPLE" and "SAMPLE" are different.
But this issue does not occur for the data source, SAMPLE1
because the same value, "SAMPLE1" is used for both the database
alias and the database name.
An example of db2dsdriver.cfg:
<configuration>
<dsncollection>
<dsn alias="PSAMPLE" name="SAMPLE" host="host.domain.com"
port="57531"/>
<dsn alias="SAMPLE1" name="SAMPLE1"
host="host.domain.com" port="57531"/>
</dsn>
</dsncollection> |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* User of IBM DS Driver Client *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to 10.5.0.3 *
**************************************************************** |
| Local Fix: |
Use same value to the dsn alias and the name parameters. |
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Problem Fixed In 10.5.0.3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.09.2013
04.03.2014
04.03.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
