db2 resource agent fails to `promote` when Master (PRIMARY DB2 DB) crashes or abrupty stops
Issue
-
When node running Master db2 resource fails/is fenced/abrupty shuts down, then the another node fails the
promoteaction of db2 resource agent with following messages in the logs.node2 lrmd: info: log_execute: executing - rsc:DB2_HADR action:promote call_id:93 db2(DB2_HADR)[xxx]: INFO: DB2 database db2inst1(0)/sample has HADR status STANDBY/PEER/CONNECTED and will be promoted db2(DB2_HADR)[xxx]: INFO: DB2 database db2inst1(0)/sample has HADR status STANDBY/DISCONNECTED_PEER/DISCONNECTED and will be promoted node2 lrmd: info: log_finished: finished - rsc:DB2_HADR action:promote call_id:93 pid:xxx exit-code:1 exec-time:13565ms queue-time:0ms
Environment
- Red Hat Enterprise Linux 7 with High-Availability or Resilient Storage Add-on
resource-agents-3.9.5-105.el7_4.2- DB2 in HADR configuration
- DB2 10.5 and DB2 11.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
