DB2 - Problem description
Problem IC93982 | Status: Closed |
WITHOUT UPGRADE_PRIOR_VERSIONS=TRUE, THE UPGRADE IS TREATED AS A NEW INSTALLATION | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
If you want to do a silent upgrade and you forget to set UPGRADE_PRIOR_VERSIONS to true in your response file, the upgrade will be treated as a new installation and will continue without error. As a consequence, in the Add/Remove program, there will be two entries for the DB2 product with the same DB2COPY name : one for the old version and one for the new version. To avoid this issue, please use the recommended method for upgrade : use UPGRADE_PRIOR_VERSIONS=YES in the response file. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.1 FP3 or above * **************************************************************** | |
Local Fix: | |
n/a | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
The problem was first fixed in DB2 10.1 FP3 Now without UPGRADE_PRIOR_VERSIONS=TRUE in the response file, the upgrade will fail. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC95503 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.07.2013 02.10.2013 02.10.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.3 | |
10.1.0.3 |