IBM Support

IT26197: DB2START MIGHT FAIL WITH SQL6036 AFTER DB2STOP TIMEOUT OCCURS

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

  • db2start might fail with SQL6036 (START or STOP DATABASE MANAGER
    command is already in progress) after db2stop timeout occurs.
    
    This problem occurs as following:
    1) db2stop starts
    2) db2stop spawns db2stop2 process and db2stop2 process has a
    lock on the file db2stst.0000
    3) db2stop timeout occurs (SQL1042C)
    4) db2stop sends SIGTERM to db2stop2 process and then db2stop
    exits
    5) Signal handler for SIGTERM in db2stop2 sends SIG_DUMP (for PD
    purpose) and sleeps for 20 seconds
    6) User calls db2_kill / ipclean since db2stop exits with
    SQL1042C and runs db2start, but db2start fails with SQL6036
    since db2stop2 still holds a lock on the file db2stst.0000
    
    The root cause is that db2stop exists before db2stop2 exits in
    the step 4).
    db2stop should wait for db2stop2 exits when db2stop timeout
    occurs.
    

Local fix

  • Run db2start more then 20 seconds after db2stop timeout.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 4 Fixpack 6 or higher                *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT26197

  • 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

    2018-09-06

  • Closed date

    2021-03-12

  • Last modified date

    2021-03-12

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

  • 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

[{"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:
13 March 2021