Symptom
During SAP HANA System Replication setup or re-registration, the secondary site does not reach ACTIVE state.
The replication repeatedly stops for one tenant database while SYSTEMDB replication appears synchronized.
The following errors are observed:
communication channel closed
connection lost during data shipping
The issue typically occurs after takeover, DR test, re-registration, or when a new secondary host is introduced.
Additional observations:
- Typically only a specific tenant database is affected
- Replication remains in Full Replica / initializing phase
- Replication restarts repeatedly
- No communication path problem can be identified
In SAP HANA traces (secondary site):
indexserver trace shows allocation failures similar to:
Out of memory (allocation failure type: GLOBAL_ALLOCATION_LIMIT)
and shortly before the replication interruption:
service unavailable
Read more...
Environment
SAP HANA DB Version 2.0
Product
Keywords
HANA System Replication, communication channel closed, Full Replica, GLOBAL_ALLOCATION_LIMIT, ReplayLogCache , 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.
SAP Knowledge Base Article - Preview