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 IC95368 Status: Closed

THE UNINSTALLER OF 64-BIT DATA SERVER CLIENT/DRIVER DOESN'T REMOVE
32BIT ODBC DATA SOURCES.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Under 64-bit Windows OS uninstallation process leaves 32-bit 
ODBC data source created by the client/driver. The problem 
doesn't apply to 64-bit ODBC data sources. Local fix is to 
manually delete a leftover registry keys.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 V10.5 on LUW users.                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 V10.5 Fix Pack 3 or higher.                    * 
****************************************************************
Local Fix:
Manually delete a leftover registry keys. The default location 
is: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI.
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 DB2 V10.5 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2013
07.04.2014
07.04.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 FixList
10.5.0.3 FixList