IBM Support

IT28023: DB2DIAG.LOG GROWING VERY FAST WITH MANY MESSAGES FROM SQLPLOGALLOCCANDIDATEPOOL::REFRESH, PROBE:60

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

  • On HADR standby, the db2diag.log file is growing very fast with
    many messages like the following:
    
    2019-01-25-18.12.54.513886+000 I4134509E612 LEVEL: Info
    PID : 17686 TID : 140122481747712 PROC : db2sysc 0
    INSTANCE: db2inst1 NODE : 000 DB : TESTDB
    HOSTNAME: host1
    EDUID : 27 EDUNAME: db2logalloc.0 (TESTDB) 0
    FUNCTION: DB2 UDB, data protection services,
    sqlpLogAllocCandidatePool::refresh, probe:60
    MESSAGE : cpStartExtPos is greater than cpEndExtPos. Forcing
    extCount to 0.
    DATA #?1 : SQLPG_EXTENT_NUM, PD_TYPE_SQLPG_EXTENT_NUM, 4 bytes
    798
    DATA #?2 : SQLPG_EXTENT_NUM, PD_TYPE_SQLPG_EXTENT_NUM, 4 bytes
    797
    
    This is a boundary condition, on a new standby database (after
    initialization or after takeover command).  The messages will
    stop after some work on the primary has generated new log files
    for the standby.  Note that in the above example, the value
    shown in DATA #1 (which is 798) is the log file number that
    would end the boundary condition (ie. the messages will stop
    when the primary database is producing log files 798 and
    beyond).
    

Local fix

  • Perform work on the primary to generate new log files for the
    standby database to process.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * HADR standbys                                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to the latest fix pack                               *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in DB2 v11.1.4.5
    

Temporary fix

  • Perform work on the primary to generate new log files for the
    standby database to process.
    

Comments

APAR Information

  • APAR number

    IT28023

  • 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

    2019-02-07

  • Closed date

    2019-10-31

  • Last modified date

    2019-10-31

  • 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:
31 October 2019