SAP Knowledge Base Article - Preview

2667371 - HANA throws out of memory dump while accessing backup catalog

Symptom

The following error occurs when opening the Backup Catalog:

'SAP DBTech JDBC [4]: cannot allocate enough memory'

KBA material.PNG



Additionally, the indexserver trace file show out of memory dumps with one of the following heap allocators as the top memory consumer:

Top "M_HEAP_MEMORY" allocators (component, name, size). Ordered descending by exclusive_size_in_use.
1: System: Pool/BackupRecoveryAllocator XX.XXgb (xxxxxxxxxxb)

Top "M_HEAP_MEMORY" allocators (component, name, size). Ordered descending by exclusive_size_in_use.
1: Monitoring & Statistical Data: Pool/RowEngine/MonitorView/StatisticsMonitors/M_DEV_BACKUP_CATALOG_LOG XX.XXgb (xxxxxxxxxxb)

 

Entries in the backup.log are observed

ERROR   LOGBCKUP state of service: nameserver, hostname:<port>, volume: 1, previous allocation failed


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

backup, HANA, oom, memory, catalog, housekeeping, dump , KBA , HAN-DB-BAC , SAP HANA Backup & Recovery , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.