Symptom
- Slowness observed in the SAP HANA database system.
- Asynchronous replication buffer full, with accumulated counts increasing over time.
- Trace logs indicate repeated occurrences of "Asynchronous replication buffer full, accumulated count = [value], trace cooldown = 300 s".
- BarrierSemaphore Wait observed in threads.
- LoggerBufferSwitch wait situations identified in logs.
-
Threads
BarrierSemaphore Wait| |LoggerBufferSwitch |no SQL (CommitTrans)
-
indexserver.trc
Line 19914: [2805657]{-1}[1942/12558338716] 2025-10-26 09:27:09.680700 i PersistenceManag DisasterRecoveryProtocol.cpp(07669) : Asynchronous replication buffer full, accumulated count = 10293, trace cooldown = 300 s
[679893]{-1}[2902/12636876161] 2025-10-27 09:28:12.571088 i PersistenceManag DisasterRecoveryProtocol.cpp(07669) : Asynchronous replication buffer full, accumulated count = 26856, trace cooldown = 300 s
Line 20053: [2805656]{-1}[1830/12563802428] 2025-10-26 10:27:09.642988 i PersistenceManag DisasterRecoveryProtocol.cpp(07669) : Asynchronous replication buffer full, accumulated count = 11444, trace cooldown = 300 s
Line 20511: [1045591]{-1}[1977/12582755121] 2025-10-26 14:27:11.933212 i PersistenceManag DisasterRecoveryProtocol.cpp(07669) : Asynchronous replication buffer full, accumulated count = 11525, trace cooldown = 300 s
Read more...
Environment
SAP HANA PLATFORM EDITION 2.0
Product
Keywords
slowness, SAP HANA, asynchronous replication buffer full, BarrierSemaphore Wait, LoggerBufferSwitch, log buffer size, log buffer count, log segment size, redo log files, system replication, I/O write regressions, savepoint bottlenecks, backup bottlenecks, logshipping_async_buffer_size, log_preformat_segment_count , KBA , HAN-DB-ENG , SAP HANA DB Engines , 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