Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC95503 Status: Closed

WITHOUT UPGRADE_PRIOR_VERSIONS=TRUE, THE UPGRADE IS TREATED AS A NEW
INSTALLATION

product:
DB2 FOR LUW / DB2FORLUW / A50 - 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:                                              * 
* DB2 LUW on Windows                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix    * 
* Pack 4) or higher.                                           * 
****************************************************************
Local Fix:
n/a
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4)
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2013
19.09.2014
19.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList