Symptom
You get errors like:
- HANA Alert ID 106 with Alert name 'ASYNC replication in-memory buffer overflow' frequently:
- On host <host:port> local in-memory buffer in ASYNC replication mode ran full ### time(s)
- Parameter 'logshipping_async_buffer_size' doesn't take effect in secondary site of a 3-teris landscape
- Mini check ID: M1818 - Async log shipping buffer full (last day) from 1999993 - How-To: Interpreting SAP HANA Mini Check Results
Trace of the affected service can show the following:
- w sr_dataaccess DisasterRecoveryConfiguration.cpp(00870) : Configured async replication buffer size too small: 16777216 -> setting to min size 16777216
- i PersistenceManag DisasterRecoveryProtocol.cpp(05762) : Asynchronous replication buffer full, accumulated count = 12031, trace cooldown = 300 s
- exception 3000321: Asynchronous Replication Buffer is Overloaded
Read more...
Environment
- 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
logshipping_async_buffer_size, logshipping_async_wait_on_buffer_full, reconnect_time_interval, Asynchronous log shipping buffer full, network throughput, network latency, M1818, secondary, HANA replication, offline, online parameter , 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