在辅助节点上停止 SAP HANA 数据库 - SAP HANA 开启 Amazon
Amazon Web Services 文档中描述的 Amazon Web Services 服务或功能可能因区域而异。要查看适用于中国区域的差异，请参阅 中国的 Amazon Web Services 服务入门 (PDF)。

本文属于机器翻译版本。若本译文内容与英语原文存在差异，则一律以英文原文为准。

在辅助节点上停止 SAP HANA 数据库

描述-在正常集群操作期间，停止主 SAP HANA 数据库（在节点 2 上）。

运行节点 — 主要 SAP HANA 数据库节点（在节点 2 上）

运行步骤：

  • 像<sid>adm在节点 2 上一样优雅地停止 SAP HANA 数据库。

    sechana:~  su - hdbadm
hdbadm@sechana:/usr/sap/HDB/HDB00> HDB stop
hdbdaemon will wait maximal 300 seconds for NewDB services finishing.
Stopping instance using: /usr/sap/HDB/SYS/exe/hdb/sapcontrol -prot
NI_HTTP -nr 00 -function Stop 400

12.11.2020 11:45:21
Stop
OK
Waiting for stopped instance using: /usr/sap/HDB/SYS/exe/hdb/sapcontrol
-prot NI_HTTP -nr 00 -function WaitforStopped 600 2


12.11.2020 11:45:53
WaitforStopped
OK
hdbdaemon is stopped.

预期结果：

  • 集群检测到已停止的主要 SAP HANA 数据库（在节点 2 上），并将辅助的 SAP HANA 数据库（在节点 1 上）提升为主数据库。

    sechana:~  crm status
Stack: corosync
Current DC: prihana (version 1.1.18+20180430.b12c320f5-3.24.1-b12c320f5)
- partition with quorum
Last updated: Thu Nov 12 11:47:38 2020
Last change: Thu Nov 12 11:47:33 2020 by root via crm_attribute on prihana

2 nodes configured
6 resources configured

Online: [ prihana sechana ]

Full list of resources:

 res_AWS_STONITH        (stonith:external/ec2): Started prihana
 res_AWS_IP     (ocf::suse:aws-vpc-move-ip):    Started prihana
 Clone Set: cln_SAPHanaTopology_HDB_HDB00 [rsc_SAPHanaTopology_HDB_HDB00]
     Started: [ prihana sechana ]
 Master/Slave Set: msl_SAPHana_HDB_HDB00 [rsc_SAPHana_HDB_HDB00]
     Masters: [ prihana ]
     Slaves: [ sechana ]

Failed Actions:
* rsc_SAPHana_HDB_HDB00_monitor_60000 on sechana 'master (failed)' (9):
call=46, status=complete, exitreason='',
    last-rc-change='Thu Nov 12 11:46:45 2020', queued=0ms, exec=0ms

  • 重叠 IP 地址已迁移到新的主地址（在节点 1 上）。

    prihana:~  ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP group default qlen 1000
    link/ether 0a:38:1c:ce:b4:3d brd ff:ff:ff:ff:ff:ff
    inet 11.0.1.132/24 brd 11.0.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet 11.0.1.75/32 scope global eth0:1
       valid_lft forever preferred_lft forever
    inet 192.168.10.16/32 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::838:1cff:fece:b43d/64 scope link
       valid_lft forever preferred_lft forever

  • 将AUTOMATIC_REGISTER参数设置为 “true” 后，集群会重新启动出现故障的 SAP HANA 数据库，并自动将其注册到新的主数据库。

恢复程序：

  • 运行crm命令清理资源后，“操作失败” 消息应从群集状态中消失。

    sechana:~  crm resource cleanup rsc_SAPHana_HDB_HDB00 sechana
Cleaned up rsc_SAPHana_HDB_HDB00:0 on sechana
Cleaned up rsc_SAPHana_HDB_HDB00:1 on sechana
Waiting for 1 replies from the CRMd. OK

  • 资源清理后，将清理群集 “失败的操作”。

    sechana:~  crm status
Stack: corosync
Current DC: prihana (version 1.1.18+20180430.b12c320f5-3.24.1-b12c320f5) - partition with quorum
Last updated: Thu Nov 12 11:50:05 2020
Last change: Thu Nov 12 11:49:39 2020 by root via crm_attribute on prihana

2 nodes configured
6 resources configured

Online: [ prihana sechana ]

Full list of resources:

 res_AWS_STONITH        (stonith:external/ec2): Started prihana
 res_AWS_IP     (ocf::suse:aws-vpc-move-ip):    Started prihana
 Clone Set: cln_SAPHanaTopology_HDB_HDB00 [rsc_SAPHanaTopology_HDB_HDB00]
     Started: [ prihana sechana ]
 Master/Slave Set: msl_SAPHana_HDB_HDB00 [rsc_SAPHana_HDB_HDB00]
     Masters: [ prihana ]
     Slaves: [ sechana ]