SAP Knowledge Base Article - Preview

3577559 - HANA replication doesn't work and Secondary_Active_Status showing Connection timeout

Symptom

HANA replication doesn't work. And from HANA Studio its observed from System Replication status overview the column 'SECONDARY_ACTIVE_STATUS' shows 'CONNECTION TIMEOUT' as does systemReplicationStatus.py.

Nameserver trace shows errors:  

[6124]{-1}[-1/-1] 2025-01-14 13:24:15.978949 e sr_nameserver    DRClient.cpp(01052) : Could not reach any host of site '2' to send request 'dr_gethdbversion'. Hosts: (<remote HANA host>:43106) Errors: 
nameserver communication error;internal error(5500)

[...]

[6124]{-1}[-1/-1] 2025-01-14 13:24:27.604512 e sr_nameserver    DRClient.cpp(01052) : Could not reach any host of site '2' to send request 'dr_replicatetopologyfromprimary'. Hosts: (<remote HANA host>:43106) Errors: 
nameserver communication error;internal error(5500)

You have already followed the solution 3260660 

"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 edition 2.0

SAP HANA Platform edition 1.0 

Product

SAP HANA 1.0, platform edition ; SAP HANA, platform edition 2.0

Keywords

system replication, Connection timeout, SECONDARY_ACTIVE_STATUS, replication status, signal 9, SIGINT, SIGQUIT, sapstart, systemReplicationStatus.py   , KBA , 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.