3688106 - SAP HANA Memory Utilization Extremely High related to hash 204c31cc9288811631f63b9a22cb6dce

You face fluctuating memory pressure which causes OOM and/or unload situations in the system, related to statement hash 204c31cc9288811631f63b9a22cb6dce.

• Checking the index server trace, you see similar entries:

  Top "M_HEAP_MEMORY" allocators (component, name, size). Ordered descending by exclusive_size_in_use.
   1: Monitoring & Statistical Data:              Pool/RowEngine/MonitorView/StatisticsMonitors                            150.89gb (162023317560b)
   2: Monitoring & Statistical Data:              Pool/Statistics/Others                                                   21.70gb (23304147184b)
   3: System:                                     Pool/BackupRecoveryAllocator                                             9.89gb (10623717308b)
   4: Monitoring & Statistical Data:              Pool/Statistics                                                          6.23gb (6691327776b)
   5: System:                                     AllocateOnlyAllocator-unlimited/FLA-UL<168,256>/BigBlockInfoAllocator    2.26gb (2434410384b)
  ....
  Top "M_CONTEXT_MEMORY" allocators (component, name, size). Ordered descending by inclusive_size_in_use.
   1: System:                                     /                                                 155.09gb (166537162582b)
   2: System:                                     StatisticsMonitors                                150.93gb (162062438304b)
   3: Monitoring & Statistical Data:              StatisticsMonitors/M_DEV_BACKUP_CATALOG_LOG_FILES 84.39gb (90619737000b)
   4: Monitoring & Statistical Data:              StatisticsMonitors/M_DEV_BACKUP_CATALOG_LOG       66.53gb (71442647640b)
   5: Statement Execution & Intermediate Results: Connection                                        2.09gb (2253195322b)
   6: Column Store Tables:                        UnifiedTableComposite                             772.32mb (809844849b)

• Checking the thread data, you see hash 204c31cc9288811631f63b9a22cb6dce as top consumer running:

  /* procedure: "_SYS_STATISTICS"."ALERT_BACKUP_LAST_LOG_FAILED" variable: CATALOG                            
  line: 13 col: 341 (at pos 1342) */ SELECT TB.STATE_NAME, TF.SOURCE_ID, TF.HOST,                             
  TV.PORT, TF.SERVICE_TYPE_NAME FROM _SYS_STATISTICS.source_alert_38_backup_catalog                           
  TB, _SYS_STATISTICS.source_alert_38_backup_catalog_files TF, _SYS_STATISTICS.source_alert_38_volumes        
  TV where TB.ENTRY_ID = TF.ENTRY_ID AND TB.ENTRY_TYPE_NAME                                                   
  = 'log backup' AND  TF.SOURCE_ID = TV.VOLUME_ID AND TB.ENTRY_ID IN (SELECT MAX(TB.ENTRY_ID)                 
  FROM _SYS_STATISTICS.source_alert_38_backup_catalog TB, _SYS_STATISTICS.source_alert_38_backup_catalog_files
  TF WHERE TB.ENTRY_TYPE_NAME = 'log backup'                                                                  
  AND TB.ENTRY_ID = TF.ENTRY_ID GROUP BY TF.SOURCE_ID)        

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.                                                 

SAP HANA, platform edition 2.0

KBA , HAN-DB-BAC , SAP HANA Backup & Recovery , HAN-DB-PERF , SAP HANA Database Performance , Problem