Symptom
- After OS patching, the secondary HANA database does not start properly.
- The secondary database does not start properly after reboot.
- The 'HDB start' command gets stuck and does not complete.
- Error messages in trace files indicate issues with nameserver communication and connection refusal, for example:
e TrexNet Responder.cpp(00579) : can't listen on port <IP Address>:4##06: (host unknown)
details: Internal Error Details: exception 1: no.2110008 (Basis/IO/Stream/impl/NetworkChannel.cpp:1159) TID: 34619
Error address in use: $msg$, rc=98: Address already in use; $[1]$=NetworkChannelBase::bindLocal. bind failed; $Context$=[971ee1c100fc82ee,<IP Address>:4##06
..
f TrexNet Responder.cpp(00907) : exception during change of listen configuration, connectivity might be lost, restart system: exception 1: no.2111000 (TrexNet/Responder.cpp:847) TID: 34619
Generic TrexNet runtime error; $INFO$=not all listeners could be started
Read more...
Environment
SAP HANA High Availability (System Replication, DR, etc.)
Product
SAP HANA, platform edition 2.0
Keywords
SAP HANA, Secondary Database, OS Patching, System Replication, Communication Error, Connection Refused, HDB start, Port Configuration. , 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.