Symptom
HANA system cannot be started and you can find similar error from traces:
- nameserver trace
[Thread ID]{-1}[5/-1] <timestamp> f NameServer TREXNameServer.cpp(03732) : Couldn't find own nameserver in topology (<hostname>:<port>)
-> stopping instance ...
[Thread ID]{-1}[5/-1] <timestamp> i DaemonClient Client.cpp(00074) : Sending signal 2
- daemon trace
[Thread ID]{-1}[-1/-1] <timestamp> i Daemon SignalsUNIX.cpp(00583) : signo 2=SIGINT from user. errno 0 code 0. Requested 'QUIT'. Sender pid <PID>, real user 'sidadm'=1001, executable 'hdbnameserver'
[Thread ID]{-1}[-1/-1] <timestamp> i Daemon Daemon.cpp(01076) : Comment file contains: nameserver: Couldn't find own nameserver in topology (<hostname>:<port>)
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 Platform 1.0
- SAP HANA Platform 2.0
Product
Keywords
topology, nameserver, startup, Sending signal 2, FAIL: process hdbdaemon HDB Daemon not , system replication, secondary, primary, backup, valid, hostname, export, unregister, un-register, hdbnsutil, Couldn't find own nameserver in topology , KBA , HAN-DB , SAP HANA Database , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , How To
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.