Symptom
When checking the status of the secondary side from the primary, column SECONDARY_ACTIVE_STATUS showing Connection timeout:
But secondary side is running:
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
Indexserver traces:
[16105]{-1}[-1/-1] 2023-03-02 08:15:41.926313 i Savepoint SavepointImpl.cpp(03108) : Snapshot current savepoint version: 530349, restart redo log position: 0x44083360e, next savepoint version: 530350, last snapshot SP version: 530349, kind: Replication, redoLogSPVersion: 530923, vid=1
[16105]{-1}[-1/-1] 2023-03-02 08:15:41.927901 i sr_dataaccess PersistenceManagerSPI.cpp(01022) : Drop and create snapshots for secondary: purpose=4, dropped snapshots=[530348], new snapshot=530349, vid=1, priHnd=0, writeAsNormalSnapshot=0
[24532]{-1}[-1/-1] 2023-03-02 08:15:42.137835 i Logger LoggerImpl.cpp(03041) : primaryBackupFinished(0x440833780)
[21168]{-1}[-1/-1] 2023-03-02 08:16:00.643764 e sr_nameserver DRClient.cpp(00955) : Could not reach any host of site '1' to send request 'dr_hasfailoverrunning'. Hosts: (abcdprdhana:40002) Errors:
nameserver communication timeout;timeout occurred(5521)
Read more...
Environment
SAP HANA Database 2.0
Product
Keywords
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