No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Huawei SAP HANA Appliance Two Node Installation Guide (RH5885H and RH8100 V3+Redhat) 10

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
HA Takeover Prerequisite

HA Takeover Prerequisite

The standby node of the cluster takes over the database only when the data synchronization the standby node and the active node is complete.

  1. Log in the primary SAP HANA server (HW00001 in this example) as the root user.
  2. Run the cd /usr/sap/hdbclient command to go to the hdbclient directory.
  3. Run the command ./hdbsql -U SAPHANAS00SR 'select distinct REPLICATION_STATUS from SYS.M_SERVICE_REPLICATION' to check the system replication status.

    • If the displayed status is active, the database has completed synchronization and remains in sync mode, and you can perform the database takeover operation.
    • If the displayed status is initializing, the database is still synchronizing data, and the database takeover operation cannot be performed.

    The process is similar to the following:

    HW00001:/ #cd /usr/sap/hdbclient
    HW00001:/usr/sap/hdbclient # ./hdbsql -U SAPHANAS00SR 'select distinct REPLICATION_STATUS from SYS.M_SERVICE_REPLICATION'

    If data synchronization is not complete, automatic HA cluster takeover will not occur. For details about manual takeover, see the SAP notes. When the synchronization status of all services is not Active, SAP does not recommend the takeover operation because this means that data may be lost.

    a. SAP note: 2578019 - Service Crashes in DataAccess::PersistenceManagerImpl::endOfDataRecovery

    Do not perform a takeover if not for all services the REPLICATION_STATUS in M_SERVICE_REPLICATION shows ACTIVE. See SAP Note 2063657 for details.

    b. SAP note: 2580302 - Emergency Shutdown of Indexserver Due to Log Position Inconsistency Upon Takeover

    With the fix the takeover in this case can succeed, but since one service wasn't in sync this implies data loss. You should follow the takeover decision guide of SAP Note 2063657 to assess if a takeover in this state is a feasible option

    c. SAP note: 2063657 - SAP HANA System Replication Takeover Decision Guideline You are advised to determine whether to perform takeover based on the site requirements.

Updated: 2019-08-27

Document ID: EDOC1100019155

Views: 35024

Downloads: 132

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next