Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC91349 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* 64-bit Windows OS                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Please See Error Description.                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please See Error Description.                                * 
****************************************************************
Local-Fix:
Manually delete a leftover registry keys. The default location 
is: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI.
verfügbare FixPacks:
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

Lösung
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC95368 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.04.2013
02.10.2013
02.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList