SAP Knowledge Base Article - Preview

2122650 - HANA oom trace file dumps with 'Composite limit violation (OUT OF MEMORY) occurred' in HANA SPS 08 and higher


  • After upgrading to SAP HANA SPS 08 and above you see Out of Memory errors and composite oom trace file dumps on HANA
  • Entries are written into the trace files similar to this:
Information about current memory composite-limit violation:
Composite limit violation (OUT OF MEMORY) occurred.
Composite limit=0
Failed to allocate 448 byte.
Current callstack:
1: 0x00007f4f0efaf9b0 in MemoryManager::LimitInfo::incrementLimitRelevantUsage(unsigned long)+0x150 at AllocatorImpl.cpp:982 (
2: 0x00007f4f0efec20d in MemoryManager::checkExplicitAllocatorLimits(unsigned long, ltt::allocator_statistics&, ltt::allocator_statistics*)+0xc9 at MemoryPool.cpp:305 (
3: 0x00007f4f0efe75ec in MemoryManager::MemoryPool::allocate(unsigned long, unsigned short, ltt::allocator_statistics&, bool&, bool, void const*)+0x368 at MemoryPool.cpp:1352 (
4: 0x00007f4f0f006e4f in MemoryManager::PoolAllocator::allocateNoThrowImpl(unsigned long, void const*)+0x6b at PoolAllocator.cpp:1041 (



  • SAP HANA, platform edition 1.0 SPS 08 and higher
  • SAP HANA, platform edition 2.0


SAP HANA 1.0, platform edition ; SAP HANA, platform edition 2.0


KBA , column store error , search table error , [9] memory allocation failed , sqlcode : 2048 , dtp , HAN-DB , SAP HANA Database , 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.