IBM Support

Automatic handling of HADR split brain after an HADR TAKEOVER BY FORCE

News


Abstract

How different versions of DB2 behave in a scenario wherein a takeover by force is issued after communication was severed between Primary and Standby and then communication is re-established later.

Content

In Versions 10.1 and below of DB2, if communication is lost between Primary and Standby and a Forced Takeover is attempted on Standby, after re-establishing communication between Old and New Primaries there is no functionality present to allow DB2 to force database shutdown on the old Primary. This could result in a potential expected Split Brain scenario.

Version 10.5 of DB2 introduces new functionality to improve in this scenario. In DB2 10.5, if a takeover by force is issued while the communication was severed between Primary and Standby, then when communication is re-established DB2 handles this by detecting the Old Primary and shutting it down by force to help prevent a potential split-brain situation.

[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"High Availability - Cluster Management","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"10.1;10.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
31 October 2018

UID

swg21962206

Page Feedback