Pacemaker's "db2" resource fails to start due to database not being in a HADR configuration

Solution Unverified - Updated -


Pacemaker's db2 resource agent fails start operations and the below error can be observed in standard logs:

$ cat /var/log/messages
Apr 26 09:03:38 node01 db2(db2_resource)[####]: ERROR: DB2 database instance/db is not in a HADR configuration but I am a M/S resource
Apr 26 09:03:38 node01 crmd[####]:  notice: Result of start operation for db2_resource on node01: 5 (not installed)
Apr 26 09:03:38 node01 crmd[####]: warning: Action 7 (db2_resource_start_0) on node01 failed (target: 0 vs. rc: 5): Error

An error of not installed can be observed from pcs status output:

$ pcs status --full
Failed Resource Actions:
* db2_resource_start_0 on node01 'not installed' (5): call=498, status=complete, exitreason='',
    last-rc-change='Tue Apr 26 09:03:34 2022', queued=1ms, exec=4455ms


  • Red Hat Enterprise Linux 7
  • Red Hat Enterprise Linux 8
  • Red Hat Enterprise Linux 9
  • Pacemaker Cluster
  • IBM DB2 managed by ocf:heartbeat:db2

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