Skip to content

Commit 0a009a8

Browse files
Fix formatting and clarify database resource status
Changed "The cluster node database resource is a primary or secondary" as “The database resource is neither primary nor secondary on any node.”
1 parent 430007f commit 0a009a8

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

support/azure/virtual-machines/linux/troubleshoot-rhel-pacemaker-cluster-services-resources-startup-issues.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -443,7 +443,7 @@ The SAP HANA resource can't be started by Pacemaker if there are `SYN` failures
443443
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
444444
node-0 DEMOTED 10 online logreplay node-1 4:S:master1:master:worker:master 5 SITEA syncmem SOK 2.00.046.00.1581325702 node-0
445445
node-1 PROMOTED 1693237652 online logreplay node-0 4:P:master1:master:worker:master 150 SITEA syncmem PRIM 2.00.046.00.1581325702 node-1
446-
```
446+
```
447447
448448
7. Exit the SAP Admin account, and then remove the cluster from maintenance mode:
449449
@@ -456,7 +456,7 @@ The SAP HANA resource can't be started by Pacemaker if there are `SYN` failures
456456
### Scenario 3, Symptom 2: SAP HANA doesn't start because of replication failure
457457

458458
SAP HANA Resource Reporting N (Standalone) mode experiences start failures with `hana_xxx_roles`.
459-
The cluster node database resource is a primary or secondary. Standalone node mode with `hana_xxx_roles` reporting **N**.
459+
The database resource is neither primary nor secondary on any node. Standalone node mode with `hana_xxx_roles` reporting **N**.
460460

461461
When you run the `sudo pcs status --full` command, the `node attributes` status is shown as follows:
462462

0 commit comments

Comments
 (0)