|
Problem IC72862
|
Status: Closed |
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 |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.5 Fix Pack 8.
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. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.11.2010
05.07.2011
05.07.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.8
|
 |
