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

IF INSTANCE IS UP WHEN DB2IUPGRADE IS ISSUED, INCORRECT MESSAGE ABOUT
DB2CKUPGRADE IS DISPLAYED

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If db2iupgrade is issued while the instance is still up running, 
the below incorrect message will be returned. 
 
 
Database Manager cannot be started. 
 
DBI1126W  Instance upgrade failed because one or more views 
defined in the database might impact database upgrade. 
 
Explanation: 
 
The db2iupgrade command calls the db2ckupgrade command. The 
instance upgrade fails if the db2ckupgrade command returns any 
errors. 
 
The db2ckupgrade command has identified one or more views that 
are dependent on database entities that have changed. This might 
cause the UPGRADE DATABASE command to fail. 
 
 
The identified views are listed in the db2ckupgrade log file. 
 
User response: 
 
Resolve the issue with the identified views or drop the views 
and then re-issue the re-issue the db2iupgrade command. After 
database  upgrade, re-create the views that you dropped. 
 
Whereas the correct message that should get displayed is 
DBI1124E Instance inst-name cannot be upgraded. 
 
Explanation: 
 
An attempt was made to upgrade an instance. This instance 
cannot be upgraded because: 
 
The instance is still active. 
Upgrading this instance is not supported. 
 
This version of the db2iupgrade command cannot be used to 
upgrade this instance. 
 
User response: 
 
Ensure that the instance is ready for upgrading and you are 
using the correct version of the db2iupgrade command. For more 
information on upgrading an instance, refer to the DB2 
Information Center.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 Version 9.7 GA servers on Linux, Unix, and           * 
* Windowsplatforms running db2ckupgrade tool.                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If db2iupgrade is issued while the instance is still         * 
* uprunning,the below incorrect message will be                * 
* returned.Database Manager cannot be started.DBI1126W         * 
* Instance upgrade failed because one or more viewsdefined in  * 
* the database might impact database upgrade.                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW Version 9.7 Fix Pack 1 or refer to        * 
* "LocalFix".                                                  * 
****************************************************************
Local Fix:
Issue db2stop and retry db2iupgrade.
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 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

Solution
The complete fix for this problem first appears in DB2 LUW 
Version 9.7 Fix Pack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.09.2009
07.04.2010
07.04.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList