SAP Knowledge Base Article - Preview

3771265 - REPLICATION_STATUS shows ACTIVE but SECONDARY_ACTIVE_STATUS shows CONNECTION TIMEOUT

Symptom

  • You want to know why REPLICATION_STATUS can be ACTIVE while there's error causing SECONDARY_ACTIVE_STATUS shows CONNECTION TIMEOUT.
  • Following error can be observed in primary site nameserver/indexserver trace.

    [2230712]{100145}[9/49910624] 2026-04-28 10:24:17.918651 e sr_nameserver    DRClient.cpp(01052) : Could not reach any host of site '2' to send request 'dr_getservers'. Hosts: (hostname:4XX06) Errors: 
    nameserver communication error;Internal Error Details: exception  1: no.8  (commlib/Impl/commlibInst.hpp:121) TID: 2230712(5500) 

"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

  • HANA System Replication
  • SAP HANA, platform edition 1.0
  • SAP HANA, platform edition 2.0

Product

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

Keywords

system replication, secondary_active_status, connection timeout, 40006, 4xx06, nameserver, metadata communication, enable_ssl, system_replication_communication, dr_getservers, nameserver communication error, firewall, port blocked, ssl connectivity , 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.