DB2 - Problembeschreibung
Problem IC72860 | Status: Geschlossen |
AFTER UPGRADING FROM DB2 VERSION 8 TO DB2 9.5 OR DB2 9.7 THE DB2 COPY NAME IS DB2COPY1 EVEN IF YOU CHOSE ANOTHER DB2 COPY NAME | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
When you run the setup command opn Windows to upgrade from DB2 version 8 to DB2 9.5 or DB2 9.7 without the -u option, it ends up with the DB2 copy name as DB2COPY1 even if you choose some other DB2 copy name. The problem does not happen if you use the -u option of the setup command to use a response file (silent installation). The problem is only when you upgrade to DB2 9.5 or DB2 9.7 not when you upgrade to DB2 9.1. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users of DB2 on Windows * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * . * **************************************************************** | |
Local-Fix: | |
As a workaround you can do either of the following: - Use the -u option of the setup command to use a response file (silent installation). - Upgrade to DB2 9.1 first, then upgrade from DB2 9.1 to your desired DB2 version. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in Version 9.7 Fix Pack 4. The problem is applicable to all DB2 Server and Client products. | |
Workaround | |
As a workaround you can do either of the following: - Use the -u option of the setup command to use a response file (silent installation). - Upgrade to DB2 9.1 first, then upgrade from DB2 9.1 to your desired DB2 version. | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC72862 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 29.11.2010 24.05.2011 24.05.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP4 | |
Problem behoben lt. FixList in der Version | |
9.7.0.4 |