3203727 - How to find the SQL statements responsible for memory growth of Join Engine

Symptom

High memory consumption due to below allocators are usually caused by expensive statements which require optimization.

If parameter statement_memory_limit or expensive statement trace is not configured, you cannot directly get the corresponding SQL Statement.

Allocator	Purpose
Pool/JoinEvaluator/JECalculate Pool/JoinEvaluator/JECalculate/TmpResults Pool/JoinEvaluator/JECreateNTuple Pool/JoinEvaluator/JEPreAggregate Pool/JoinEvaluator/JEStep1 Pool/JoinEvaluator/JEStep2 Pool/JoinEvaluator/NTuple	Join engine intermediate data structures
Pool/JoinEvaluator/JEAggregate Pool/JoinEvaluator/JEAggregate/Results Pool/JoinEvaluator/JEAssembleResults Pool/JoinEvaluator/JEAssembleResults/Results Pool/JoinEvaluator/JECalculate/Results Pool/JoinEvaluator/JERequestedAttributes/Results	Join engine results

Environment

SAP HANA platform 1.0
SAP HANA platform 2.0

Product

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

Keywords

top allocator, consumer, JoinEngine, composite OOM, statement_memory_limit, M_EXPENSIVE_STATEMENT , KBA , HAN-DB-PERF , SAP HANA Database Performance , How To

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.