Symptom
-
In transaction ST22, memory-related dumps are visible. For example: SYSTEM_NO_TASK_STORAGE, STORAGE_PARAMETERS_WRONG_SET, DBSQL_NO_PERM_MM_MEMORY, DBSQL_DBSL_NO_MEMORY or SYSTEM_NO_MEMORY.
-
In the corresponding work process trace file (dev_w*). Located in the instance's work directory (LocalDrive\usr\sap\<SID>\SCS<XX>\work), the below entries can be seen 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]
X {root-id=CC43E7E7AB881ED786938A6A4C4F01C7}_{conn-id=00000000000000000000000000000000}_0 -
Accessing transaction SE38 in the instance. Where the dump was raised and running the RSMEMORY report, in the PROC Memory box, click Server as per the below image:
And on the output screen where the current usage of PROC Memory in the server is shown, it can be seen that the Glob. Quota column value was reached by the Glob. Peak value and/or by the Glob. Used value. This means that the PROC memory global quota was completely exhausted in the instance, as per the below image:
Read more...
Environment
- SAP NetWeaver 7.4
- SAP NetWeaver 7.5
- SAP NetWeaver Application Server for SAP S/4HANA
- ABAP PLATFORM - Application Server ABAP
Product
Keywords
CST, client server technology, kernel, application server, instance, 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, work directory, LocalDrive\usr\sap\<SID>\SCS<XX>\work, em/proc_use_stdheap=TRUE, DBSQL_DBSL_NO_MEMORY , KBA , BC-CST-MM , Memory Management , BC-DB-DBI , DB Independent Database Interface , Problem
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.