SAPHana Resource Experiencing Start Failures with hana_xxx_roles Reporting N (Standalone)

Solution Verified - Updated -

Issue

Database resource does not primary or secondary on either node. With hana_xxx_roles reporting N for Standalone node mode.

Node Attributes:
  * Node: Node1 (1):
    * hana_xxx_clone_state              : UNDEFINED 
    * hana_xxx_op_mode                  : logreplay 
    * hana_xxx_remoteHost               : Node.remote.host.name
    * hana_xxx_roles                    : 1:N:master1::worker:           <<<<<
    * hana_xxx_site                     : sap_site  
    * hana_xxx_srah                     : -         
    * hana_xxx_srmode                   : syncmem   
    * hana_xxx_sync_state               : SFAIL     
    * hana_xxx_version                  : 2.00.067.03
    * hana_xxx_vhost                    : sap.vhost.name
    * lpa_xxx_lpt                       : 10        
  * Node: Node2 (2):
    * hana_xxx_clone_state              : DEMOTED   
    * hana_xxx_op_mode                  : logreplay 
    * hana_xxx_remoteHost               : Node.remote.host.name
    * hana_xxx_roles                    : 4:N:master1:master:worker:master           <<<<<
    * hana_xxx_site                     : sap_site  
    * hana_xxx_srah                     : -         
    * hana_xxx_srmode                   : syncmem   
    * hana_xxx_version                  : 2.00.067.03
    * hana_xxx_vhost                    : sap.vhost.name
    * lpa_xxx_lpt                       : 1711641128

With migration summary reporting INF fail-count with failed SAPHana resource action reporting start failures due to "not running."

Migration Summary:
  * Node: Node1 (1):
    * SAPHana_Resource: migration-threshold=5000 fail-count=1000000 last-failure='Thu Mar 28 09:39:07 2024'
  * Node: Node2 (2):
    * SAPHana_Resource: migration-threshold=5000 fail-count=1000000 last-failure='Thu Mar 28 09:23:06 2024'

Failed Resource Actions:
  * SAPHana_Resource_start_0 on Node1 'not running' (7): call=97, status='complete', last-rc-change='Thu Mar 28 09:39:06 2024', queued=0ms, exec=1014ms
  * SAPHana_Resource_start_0 on Node2 'not running' (7): call=27, status='complete', last-rc-change='Thu Mar 28 09:23:05 2024', queued=0ms, exec=1024ms

You may additionally see the below HANA_STATE_DEFECT error for monitor operations on the primary node:

Aug 18 05:04:52  rhel8-node1 SAPHana( SAPHana_RH2_00)[305954]: INFO: RA ==== begin action monitor_clone (0.154.0) ====
Aug 18 05:04:52  rhel8-node1 SAPHana( SAPHana_RH2_00)[305954]: INFO: RA: SRHOOK1=
Aug 18 05:04:52  rhel8-node1 SAPHana( SAPHana_RH2_00)[305954]: INFO: RA: SRHOOK2=PRIM
Aug 18 05:04:52  rhel8-node1 SAPHana( SAPHana_RH2_00)[305954]: INFO: RA: SRHOOK3=PRIM
Aug 18 05:04:54  rhel8-node1 SAPHana( SAPHana_RH2_00)[305954]: WARNING: ACT: saphana_monitor_clone: HANA_STATE_DEFECT <---
Aug 18 05:04:54  rhel8-node1 SAPHana( SAPHana_RH2_00)[305954]: INFO: RA ==== end action monitor_clone with rc=1 (0.154.0) (3s)====
Aug 18 05:04:54  rhel8-node1 pacemaker-controld[4065]: notice: Result of monitor operation for  SAPHana_RH2_00 on  rhel8-node1: error

Environment

  • Red Hat High Availability Cluster
  • Red Hat Enterprise Linux 8, 9
  • SAPHana

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