IBM Support

IT04972: A LOG FILE ON STANDBY NEVER GETS UPDATED/RESIZED WHEN NEW LOG FILE SIZE INTRODUCES IN ITS PREVIOUS EXTENT

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

  • During log file size change, when customer runs deactivate db(or
    db2stop) twice on HADR Primary, A log file on HADR Standby never
    gets updated/resized when new log file size introduces in its
    previous extent. that's because, If there's an empty extent with
    incorrect log file size in standby active log path, Standby
    doesn't check the log file size, so it blindly thinks the log
    file is good. if customer issues db2stop/reactivate db on HADR
    Standby while meeting this issue, Standby will mistakenly
    truncate the log file, and will fail to connect to Primary due
    to pair validation errors.
    
    you might see below messages in db2diag.log of Standby, when we
    hit this APAR, Note:NextFormatExtNum 136867 is missed.
    
    i.e
    
    2014-07-27-02.05.35.233516-300 I11101A431         LEVEL: Info
    PID     : 11927608             TID  : 10282       PROC : db2sysc
    0
    INSTANCE: db2sm1               NODE : 000         DB   : SM1
    EDUID   : 10282                EDUNAME: db2hadrs (SM1) 0
    FUNCTION: DB2 UDB, High Availability Disaster Recovery,
    hdrSPrepareLogWrite, probe:10330
    DATA #1 : <preformatted>
    NextFormatExtNum 136866, create log file with firstlso
    28649961820385
    
    
    2014-07-27-02.15.10.521227-300 I62104A431         LEVEL: Info
    PID     : 10616928             TID  : 10282       PROC : db2sysc
    0
    INSTANCE: db2sm1               NODE : 000         DB   : SM1
    EDUID   : 10282                EDUNAME: db2hadrs (SM1) 0
    FUNCTION: DB2 UDB, High Availability Disaster Recovery,
    hdrSPrepareLogWrite, probe:10330
    DATA #1 : <preformatted>
    NextFormatExtNum 136868, create log file with firstlso
    28650496069857
    

Local fix

  • when we see the problem, customer just needs to manully remove
    the problematic log file and reactivate the database on HADR
    Standby.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * First Fixed in DB2 9.7 Fix Pack 11                           *
    ****************************************************************
    

Problem conclusion

  • First Fixed in DB2 9.7 Fix Pack 11
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT04972

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-10-16

  • Closed date

    2017-05-09

  • Last modified date

    2017-05-09

  • 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

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IT04972

Modified date: 09 May 2017