home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC66095 Status: Geschlossen

FAIL TO UNINSTALL THE ONLY DEFAULT DB2 COPY IF A MERGE MODULE DB2 COPY
COEXISTS ON 64BIT WINDOWS

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When users try to uninstall the only DB2 copy on a 64bit Windows 
system where a merged module DB2 copy exists, uninstallation 
will fail with error message "switch the default copy to another 
copy". This is incorrect as the merged module DB2 copy cannot be 
the default copy and hence there should not be any error to 
uninstall the DB2 copy even though it is the current default DB2 
copy.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* 64Bit Windows with a merged module DB2 copy                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When users try to uninstall the only DB2 copy on a 64bit     * 
* Windows                                                      * 
* system where a merged module DB2 copy exists, uninstallation * 
*                                                              * 
* will fail with error message "switch the default copy to     * 
* another                                                      * 
* copy". This is incorrect as the merged module DB2 copy       * 
* cannot be                                                    * 
* the default copy and hence there should not be any error to  * 
*                                                              * 
* uninstall the DB2 copy even though it is the current default * 
* DB2                                                          * 
* copy.                                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 v9.7 FP2 and up.                               * 
****************************************************************
Local-Fix:
To workaround this problem, add the following registry to the 
system from a command windows using this command: 
reg add 
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\InstalledCopies\[DB2_COPY_NA 
ME] 
/v IsMergeModuleCopy /t REG_SZ /d YES 
E.g., 
reg add 
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\DB2\InstalledCopies\DB2COPY1 /v 
IsMergeModuleCopy /t REG_SZ /d YES
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Fixed in DB2 v9.7 Fixpack 2.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.02.2010
13.05.2010
13.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList