In transaction ST22 of your system you can see the memory dumps such as SYSTEM_NO_TASK_STORAGE, DBSQL_NO_PERM_MM_MEMORY, DBSQL_DBSL_NO_MEMORY or SYSTEM_NO_MEMORY raised as per the below image.
In the work process trace file responsible for raising the dump you can see the below error entry created in the same timestamp of the dumps.
X Mon Apr 4 11:35:29 2017
X *** ERROR => Total heap memory usage (PRIV=87988224, PROC=6706098952+4926600) exceeds global PROC quota=6706098952 [emxx.c 5104]
Accessing transaction SE38 in the instance where the dump was raised and running the RSMEMORY report, in the PROC Memory box you click on "Server", as per the below image.
In the output screen where the current usage of PROC Memory in the server is shown you can see that Glob. Quota column value was reached by the Glob. Peak value and/or Glob. Used. This means that PROC memory global quota was completely exhausted in the instance, as per the below image:
SAP NetWeaver release 7.4x
DBSQL_NO_PERM_MM_MEMORY memory db_allocate_heap_block heap, PROC, memory, dump, hanging, crash, TSV_TNEW_PAGE_ALLOC_FAILED, SYSTEM_NO_ROLL, LOAD_NO_ROLL, GEN_INTERNAL_ERROR, heap. em/proc_max_size_MB, DBSQL_ALLOCATION_FAILED, em/proc_max_wpsize_MB , KBA , BC-CST-MM , Memory Management , BC-DB-DBI , DB Independent Database Interface , Problem
About this pageThis 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.