IBM Support

Db2 HADR with Pacemaker - Allow VIP failover to occur before primary reintegration

How To


Summary

In a force takeover scenario, the VIP resource is only moved once the old Primary is able to successfully reintegrated as the new Standby node. Waiting for the old Primary to reintegrate as Standby causes a delay in moving the VIP to the new Primary even though takeover HADR command completed.

An update to the Pacemaker resource model can change this default behavior and allow the VIP to move to the new Primary earlier.

Document Location

Worldwide

[{"Type":"MASTER","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"},"ARM Category":[{"code":"a8m500000008PlzAAE","label":"HADR-\u003ETakeover"},{"code":"a8m3p0000006xc1AAA","label":"High Availability-\u003EPacemaker"}],"ARM Case Number":"TS020651228","Platform":[{"code":"PF016","label":"Linux"}],"Version":"11.5.9"},{"Type":"MASTER","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"},"ARM Category":[{"code":"a8m3p0000006xc1AAA","label":"High Availability-\u003EPacemaker"}],"Platform":[{"code":"PF016","label":"Linux"},{"code":"PF055","label":"zLinux"}],"Version":"and future releases;12.1.5"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
30 June 2026

UID

ibm17257496