IBM Support

IT27015: WITH A ROTATING DB2 DIAGNOSTIC LOG, CERTAIN MESSAGES FROM THE DB2HAVEND PROCESS WILL BE LOGGED TO THE DEFAULT DB2DIAG.LOG FILE

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

  • In the environments where a rotating Db2 diagnostic log is
    enabled, i.e. where:
    $ db2 get dbm cfg | grep DIAGSIZE
    shows a non-zero value, certain messages from db2havend process,
    which is responsible for the interaction between Db2 engine and
    high availability software (e.g. IBM TSAMP), will always be
    logged to the default file named db2diag.log and not the
    rotating one (one, with a numerical suffix, e.g.
    db2diag.10.log). This is an example of a message of this kind
    (note PROC : db2havend):
    
    2018-11-02-05.26.49.624162-420 I2105E413             LEVEL:
    Event
    PID     : 15235                TID : 47713327275008  PROC :
    db2havend (db2ha)
    INSTANCE: db2v111              NODE : 000
    HOSTNAME: db2ha1.ibm.com
    FUNCTION: DB2 UDB, high avail services,
    db2haEnableResourceGroup, probe:10359
    MESSAGE : Issuing unlock request against resource group.
    DATA #1 : String, 29 bytes
    db2_db2v111_db2v111_SAMPLE-rg
    
    This APAR will address this behavior.
    

Local fix

Problem summary

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

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT27015

  • 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-11-18

  • Closed date

    2020-01-16

  • Last modified date

    2020-01-16

  • 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

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"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 January 2020