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 IT21940 Status: Closed

FIXPACK UPDATE GETS ERRORS FOR NOT EXIST "DB2" INSTANCE.

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Here is an example problem reproducible scenario. 
 
1.  Install V105FP4 
    * This will by default create ESE instance named "DB2" 
 
2.  db2icrt -s wse newdb2 -u:db2admin,insT4Win 
 
3.  db2icrt -s wse newdb2y -u:db2admin,insT4Win 
 
4.  db2ilist will display three instances as below: 
    DB2 
    DB2NEW 
    DB2NEWY 
 
5.  db2set -all will show below 
    C:\Program Files\IBM\SQLLIB\BIN>db2set -all 
    [e] DB2PATH=C:\Program Files\IBM\SQLLIB 
    [i] DB2INSTOWNER=VMINSTWIN14 
    [i] DB2PORTRANGE=60000:60005 
    [i] DB2INSTPROF=C:\PROGRAMDATA\IBM\DB2\DB2COPY1 
    [i] DB2COMM=TCPIP 
    [g] DB2_EXTSECURITY=YES 
    [g] DB2_COMMON_APP_DATA_PATH=C:\ProgramData 
    [g] DB2SYSTEM=VMINSTWIN14 
    [g] DB2PATH=C:\Program Files\IBM\SQLLIB 
    [g] DB2INSTDEF=DB2 
    [g] DB2ADMINSERVER=DB2DAS00 
 
6.  db2stop 
 
7.  db2idrop DB2 (drop "DB2" instance) 
    * We will get a message that no default instance has been 
set. 
 
8.  After deleting DB2 instance. the output of db2set -all is as 
below. 
    * this does not show DB2INSTDEF 
    C:\Program Files\IBM\SQLLIB\BIN>db2set -all 
    [e] DB2PATH=C:\Program Files\IBM\SQLLIB 
    [g] DB2_EXTSECURITY=YES 
    [g] DB2_COMMON_APP_DATA_PATH=C:\ProgramData 
    [g] DB2SYSTEM=VMINSTWIN14 
    [g] DB2PATH=C:\Program Files\IBM\SQLLIB 
    [g] DB2ADMINSERVER=DB2DAS00 
 
9.  Try to do Fixpack update to V105FP6, gets errors for not 
exist "DB2" instance unexpectedly. 
    * Unable to upgrade configuration file. 
 
Root cause: 
   Installer checks/uses default "DB2" instance even if it's 
dropped already. 
 
Symptom: 
   Can not upgrade and setup.trc records not exist default "DB2" 
instance name. 
 
Condition of problem: 
   When the default instance "DB2" has been dropped. 
 
Workaround: 
   Do not drop the default "DB2" instance.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Db2 Version 11.1                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 Version 11.1 Mod 3 Fix Pack 3.                * 
****************************************************************
Local Fix:
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Db2 Version 11.1 Mod 3 Fix Pack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.08.2017
16.03.2018
16.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)