IBM Support

IZ37223: HADR STANDBY DB CRASHES AFTER PRIMARY-REINTEGRATION WITH A LOG F ILE SIZE CHANGE - "STARTING LSN > ENDING LSN"

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In an HADR environment with machine A (Primary) and machine B
    (Standby)
    1) On B: takeover hadr on db <db> by force
    2) On A: deactivate db <db>
    3) On B: update db cfg for db <db> using logfilsiz <newsize>
    4) On B: deactivate db <db>
    5) On B: start hadr on db <db> as primary by force
    6) On B: (run log-generating workloads)
    7) On A: start hadr on db <db> as standby
    For this last step, the start succeeds, but shortly
    afterwards the Standby database crashes during the
    remote-catchup phase of hadr with a message similar to the
    following in db2diag.log
    2008-11-12-10.58.31.706373-480 I191873E528   LEVEL: Error
    PID : 12506         TID  : 46916021991792PROC :
    db2redom (HADRDB)
    INSTANCE: aihenner        NODE : 000   DB   : HADRDB
    APPHDL : 0-18         APPID: *LOCAL.DB2.081112185831
    FUNCTION: DB2 UDB, recovery manager, sqlpshrScanOpen,
    probe:96500
    MESSAGE : Error: shrScanStartLsn 0000000000FA000C >
    shrScanEndLsn
       0000000000F9FFFB. rc =
    DATA #1 : Hexdump, 4 bytes
    0x00007FFF36D7EB50 : 1100 1082
    ....
    2008-11-12-10.58.31.706631-480 I192402E481   LEVEL: Error
    PID : 12506         TID  : 46916021991792PROC :
    db2redom (HADRDB)
    INSTANCE: aihenner        NODE : 000   DB   : HADRDB
    APPHDL : 0-18         APPID: *LOCAL.DB2.081112185831
    FUNCTION: DB2 UDB, recovery manager,
    sqlpChangeLogFileSizeDuringRecovery, probe:180
    RETCODE : ZRC=0x82100011=-2112880623=SQLPSHR_ERR_SCANRANGE
       "Attempted to open a log scan with starting LSN >
    ending LSN"
    

Local fix

  • Restart the standby
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of DB2 High Availability Disaster Recovery (HADR)  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Standby crashes during primary reintegration when replaying  *
    * a log file size change.                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 9.1 Fixpack 7                         *
    ****************************************************************
    

Problem conclusion

  • Fixed in DB2 Version 9.1 Fixpack 7
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ37223

  • Reported component name

    DB2 HAFW

  • Reported component ID

    5724N8200

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-11-12

  • Closed date

    2009-04-06

  • Last modified date

    2009-04-06

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

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

    IZ39730

Fix information

  • Fixed component name

    DB2 HAFW

  • Fixed component ID

    5724N8200

Applicable component levels

  • R910 PSN

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]

Document Information

Modified date:
03 October 2021