After Failover of "db2" resource the secondary fails to start reporting error code SQL1768N or SQL1776N

Solution Verified - Updated -

Issue

  • After Failover the secondary server is consistently not able to start the DB2 resource, and will throw error SQL1768N Reason code = 19 as start failure reason:

    Aug 14 13:44:51 rhel8-node2 db2(db2-resource1)[442750]: ERROR: DB2 database archive(0)/ARCHIVE didn't start: SQL1768N  Unable to start HADR. Reason code = "19".
Aug 14 13:44:51 rhel8-node2 pacemaker-controld[235228]: notice: Result of start operation for db2-resource1 on 
rhel8-node2: error

  • You may additionally see SQL1776N Reason code 6 with this issue:

    May 30 14:17:53 rhel8-node2 db2(db2-resource1)[258101]: ERROR: DB2 database archive(0)/ARCHIVE didn't start: SQL1776N  The command cannot be issued on an HADR database. Reason code = "6"
May 30 14:17:53 rhel8-node2 pacemaker-controld[6015]: notice: Result of start operation for db2-resource1 on rhel8-node2: error

Environment

  • Red Hat Enterprise Linux 7, 8, and 9 with the High Availability Add On
  • Pacemaker
  • IBM db2 resource agent

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