Symptom
- After enabling system replication, you try to start HANA DB system on the secondary site but it failed to start.
- In the nameserver.trc file you see the following:
sr_nameserver TREXNameServer.cpp(17363) : starting in system replication mode
sr_nameserver TREXNameServer.cpp(15174) : replication of topology from primary site was successful
sr_nameserver Utils.cpp(00323) : no disaster recovery mapping defined, please re-run hdbnsutil -sr_register
NameServer TREXNameServer.cpp(03673) : error in topology, cannot start as secondary site -> stopping instance ...
or
sr_nameserver TREXNameServer.cpp(11043) : starting in system replication mode
sr_nameserver Utils.cpp(00719) : no disaster recovery mapping defined, please re-run hdbnsutil -sr_register
NameServer TREXNameServer.cpp(03356) : error while updating topology after drReplicateTopology -> stopping instance ...
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Read more...
Environment
- SAP HANA 1.0, PLATFORM EDITION
- SAP HANA 2.0, PLATFORM EDITION
Product
Keywords
error in topology, error while updating topology, drReplicateTopology , 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 for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview