SAP Knowledge Base Article - Preview

3335389 - Slow initialisation and memory OOM on tertiary site in Multitier System Replication on HANA DB

Symptom

  • Slow initialisation of system replication tertiary site.
  • Tertiary site experiences Global Out Of Memory dumps.
  • The OOM runtime dumps show the top allocator as similar to:

Top "M_HEAP_MEMORY" allocators (component, name, size). Ordered descending by exclusive_size_in_use.
 1: System:                                     Pool/PersistenceManager/DisasterRecoverySecondary/ReplayLogCache       4gb (4294967296b)


Read more...

Environment

SAP HANA Platform 2.0

Product

SAP HANA, platform edition all versions

Keywords

 M_HEAP_MEMORY, allocators, exclusive_size_in_use,Pool/PersistenceManager/DisasterRecoverySecondary/ReplayLogCache, initialisation, sr_register, re-sync
, 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.