SAP Knowledge Base Article - Preview

3132131 - An expected failover didn't occur even though a standby host is configured correctly.

Symptom

In a muiti-host landscape, a failover to a standby host from the failed host didn't occur.
The all hosts are belonging to the same failover actual group(default).

> python $DIR_INSTANCE/exe/python_support/landscapeHostConfiguration.py
----------------------------------------------------------------------------------------------
| Host               | Host   | Host     | Failover           | Failover | Failover| NameServer | NameServer | IndexServer | IndexServer | Host                   | Host                     | Worker | Worker |
|                      | Active | Status  | Status             | Config   | Actual   | Config         | Actual          | Config          | Actual         | Config                 | Actual                  | Config   | Actual |
|                      |          |             |                       | Group   | Group   | Role             | Role            | Role             | Role            | Roles                  | Roles                    | Groups | Groups |
| --------------   | ------ | --------  | ----------------  | -------- | -------- | ------------- | -------------- | -------------- | ------------- | -------------------- | -------------------- | -------- | ------- |
| masterhost1   |  yes   | ok         |                       |  default |  default | master 1     | master         | worker         | master        | worker xs_worker | worker xs_worker | default  | default |
| failedhost1     |   no   | warning  | waiting 10 sec |  default |  default | master 2     | slave            | worker         | slave           | worker                | worker                 | default  | default |
| standbyhost |  yes   | ignore    |                       |  default |  default | master 3     | slave            | standby       | standby       | standby               | standby                | default  | default |

The failed failover can be found from master nameserver trace as below.
[6787]{-1}[-1/-1] 2021-12-02 11:28:19.881325 i service_active_s TREXNameServer.cpp(04149) : Service active states (setInactive - failedhost1:38401, watchdog=0):
[6787]{-1}[-1/-1] 2021-12-02 11:28:19.881342 i service_active_s TREXNameServer.cpp(04163) : - masterhost1: 16484=yes,38400=yes,38401=yes,38402=yes,38403=yes,38404=yes,38406=yes,38407=yes,38410=yes,38429=yes,38431=yes
[6787]{-1}[-1/-1] 2021-12-02 11:28:19.881351 i service_active_s TREXNameServer.cpp(04163) : - failedhost1: 38400=no,38401=no,38402=no,38403=no,38406=no,38410=no,38440=no
[6787]{-1}[-1/-1] 2021-12-02 11:28:19.881356 i service_active_s TREXNameServer.cpp(04163) : - standbyhost: 38400=yes,38401=yes,38402=yes,38406=yes,38410=yes
............
[6956]{-1}[-1/-1] 2021-12-02 11:28:48.471996 w failover TREXNameServer.cpp(05864) : no hosts available to handle failing host failedhost1, retrying later
[6950]{-1}[-1/-1] 2021-12-02 11:29:18.474162 w failover TREXNameServer.cpp(05864) : no hosts available to handle failing host failedhost1, retrying later
[6950]{-1}[-1/-1] 2021-12-02 11:29:18.474748 w failover TREXNameServer.cpp(05870) : no hosts available to handle failing host failedhost1, retrying later but without further tracing
[6950]{-1}[-1/-1] 2021-12-02 11:29:18.474875 w failover TREXNameServer.cpp(05874) : topology for all hosts=

The related failover parameter 'nameserver.ini/[failover]/cross_failover_group' has been set to 'true'.


Read more...

Environment

HANA 2.0

Product

SAP HANA, platform edition 2.0

Keywords

failover, standby, no hosts available to handle failing host , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.