IBM Support

IT32198: INSTALLFIXPACK TRIES TO EXIT MAINTENANCE MODE WHEN IT SHOULDN'T

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • installFixPack fails with the following output:
    
    TSA version installed on this host : y.y.y.y
    TSA version present on the media : y.y.y.y
    TSA version after update : y.y.y.y
    
    GPFS version installed on the host: x.x.x.x
    GPFS version present on the media : x.x.x.x
    GPFS version after update : x.x.x.x
    
    Tasks needed for performing Fixpack update :
    ============================================
    1 : Stopping the instance on the local host
    2 : Exiting cluster management software out of maintenance mode
    
    ...
    
    Exiting cluster management software out of maintenance mode task
    of a rolling update operation failed.
    Execution of a rolling update task failed with an error.
    Error message:
    "Host 'HOSTNAME' is currently not in maintenance mode."
    
    
    the installFixPack operation cannot exit maintenance mode if
    it never entered maintenance mode to being with. This error
    happens when both the GPFS and TSA versions are the same
    on the media and on system; it doesn't attempt to go into
    maintenance mode to update those software.
    

Local fix

  • on the node where installFixPack failed, the TSA and GPFS has
    already been updated to the target fix pack's required version
    so there is no need to go into maintenance again. Simply finish
    the installFixPack manually by running the following commands:
    
    1. <target_FP_dir>/bin/db2cluster -cm -verify -maintenance
    (ensure its not in maintenance mode)
    2. <target_FP_dir>/bin/db2cluster -cfs -verfiy -maintenance
    (ensure its not in maintenance mode)
    3. <target_FP_dir>/instance/db2iupdt -d -ru_internal_flag
    -online <instance_id>
    4. login as instance id
    5. db2start instance on <hostname>
    5. db2start member <member_id> or db2start cf <cf_id> (depending
    on whether the node hosts a member or cf)
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * all                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to db2_v111m4fp6 or later                            *
    ****************************************************************
    

Problem conclusion

  • Upgrade to db2_v111m4fp6 or later
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT32198

  • 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

    2020-03-17

  • Closed date

    2020-03-23

  • Last modified date

    2020-09-24

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

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

    IT36058

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

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

Document Information

Modified date:
27 February 2021