|
Problem IC70622
|
Status: Closed |
DB2 CATALOG USER ODBC DATA SOURCE DOES NOT UPDATE DB2CLI.INI |
| product: |
DB2 CONNECT / DB2CONNCT / 970 - DB2 |
| Problem description: |
On Windows 64 bits, if you try to catalog your database as an
ODBC data source with the following command :
db2 catalog user odbc data source <name>, you will get a message
that the command completed successfully even if the file
db2cli.ini is not updated with the correct information. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All Windows users *
****************************************************************
* PROBLEM DESCRIPTION: *
* DB2 CATALOG USER ODBC DATA SOURCE IS NOT UPDATING *
* DB2CLI.INI *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2_v97fp3a or later versions *
**************************************************************** |
| Local Fix: |
As a workaround, you can :
- manually update db2cli.ini with the correct DBALIAS
or
- run db2 update cli cfg at user level for section <name>
using DBALIAS <name> |
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Added code to increase the array size. Fixed in V97fp3a. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC71114
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.08.2010
11.11.2010
11.11.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3A
|
| Problem solved according to the fixlist(s) of the following version(s) |
