A db2 resource failed to promote to master after a cluster node was fenced or rebooted

Solution In Progress - Updated -

Issue

A db2 resource failed to promote to master after a cluster node was fenced or rebooted.

Jun 12 14:35:28 node42 pengine[5767]:  notice:  * Promote    DB2_HADR:0     (   Slave -> Master node42 )
Jun 12 14:35:29 node42 crmd[5768]:  notice: Initiating promote operation DB2_HADR_promote_0 locally on node42
Jun 12 14:35:29 node42 db2(DB2_HADR)[12339]: INFO: DB2 database db2inst1(0)/sterdb has HADR status STANDBY/REMOTE_CATCHUP_PENDING/DISCONNECTED and will be promoted
Jun 12 14:35:29 node42 crmd[5768]:  notice: Result of promote operation for DB2_HADR on node42: 1 (unknown error)
Jun 12 14:35:29 node42 crmd[5768]: warning: Action 6 (DB2_HADR_promote_0) on node42 failed (target: 0 vs. rc: 1): Error

Environment

  • Red Hat Enterprise Linux Server 7, 8 (with the High Availability Add On)
  • pacemaker

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content