|
Problem IC92230
|
Status: Closed |
DB2CLI REGISTERDSN -ADD -ALLDSN SYSTEM HAS MISSING ODBC DSNs WITH A LARGE NUMBER OF DSNs IN DB2CLI.INI OR DB2DSDRIVER.CFG |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When using the db2cli command to register ODBC datasources with
a command such as this:
db2cli registerdsn -add -alldsn -system
Some of the datasources may not be registered if there are a
large number of DSNs defined in the db2cli.ini file or
db2dsdriver.cfg file. If the total length of DSN names combined
exceeds 2050 characters, it will lead to this particular issue. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Windows *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v10.1 Fixpack 3 *
**************************************************************** |
| Local Fix: |
Reduce the amount of DSNs defined |
| available fix packs: |
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 Fixpack 3 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC95467
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.05.2013
07.10.2013
07.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
