IBM Support

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

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error 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.
    

Local fix

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.                *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in Db2 Version 11.1 Mod 3 Fix Pack 3.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT21940

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-08-09

  • Closed date

    2018-03-16

  • Last modified date

    2018-03-16

  • APAR is sysrouted FROM one or more of the following:

    IT13117

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 March 2018