IBM Support

LI73482: HADR primary and standby database synchronization performance issues.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A delay in the setting of HADR state S-NearlyPeer from
    S-RemoteCatchup during database synchronization between primary
    and standby databases is addressed via this fix.
    An HADR environment may hit this issue in the following
    situation:
    1) Standby database is deactivated
    2) Execute transactions against the primary database and archive
    log
    3) Standby database is activated
    Once the secondary database is again active, a connection to the
    primary database is established, the log file is sent to the
    standby database to facilitate synchronization between the two
    databases. This is the point where the observed delay is
    experienced.
    The following is a snippet from a standby db2diag.log which was
    captured in such a situation. Note the delay in the following
    snippet:
    yyyy-mm-dd-10.41.27.317333+540 E3260281A339 LEVEL: Event
    PID : nnnnn TID : 2199111659072PROC : db2hadrs (xxxxxxxx) 0
    INSTANCE: xxxxxxxx NODE : nnn
    FUNCTION: DB2 UDB, High Availability Disaster Recovery,
    hdrSetHdrState, probe:10000
    CHANGE : HADR state set to S-RemoteCatchup (was
    S-RemoteCatchupPending)
    yyyy-mm-dd-10.57.58.536744+540 E3260934A329 LEVEL: Event
    PID : nnnnn TID : 2199111659072PROC : db2hadrs (xxxxxxxx) 0
    INSTANCE: xxxxxxxx NODE : nnn
    FUNCTION: DB2 UDB, High Availability Disaster Recovery,
    hdrSetHdrState, probe:10000
    CHANGE : HADR state set to S-NearlyPeer (was S-RemoteCatchup)
    

Local fix

Problem summary

  • A delay in the setting of HADR state S-NearlyPeer from
    S-RemoteCatchup during database synchronization between primary
    and standby databases is addressed via this fix.
    

Problem conclusion

  • Problem was first fixed in DB2 UDB Version 9.5 FixPack 4.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI73482

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-06-05

  • Closed date

    2009-05-28

  • Last modified date

    2009-05-28

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

    LI73466

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

Fix information

  • Fixed component name

    DB2 UDE ESE LIN

  • Fixed component ID

    5765F4104

Applicable component levels

  • R950 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":"950","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
28 May 2009