If You are experiencing high memory consumption / out of memory situations . SAP is asking you to generate a runtime dump for further analysis.
This blog with help you to generate a runtime dump in HANA database.
Easiest way to generate runtime dump is from OS Level:
1) Log into the HANA host as sidadm user
2) Run command ‘hdbcons’
3) On the hdbcons console run command below
> runtimedump dump
This will create a runtimedump for the host . runtime dump file will be under traces directory with naming like ‘indexserver….rtedump.trc’.
Generate runtime dump from Python script from OS level:
<HOSTNAME>:/usr/sap/<>SID/HDB10/exe/python_support> python fullSystemInfoDump.py -t <TENANT SID> –rtedump
System Info Dump created 2019-07-22 11:13:07 (UTC) with script version 2.00
Called with command line options: -t <TENANT SID> –rtedump
Writing to file /usr/sap/<SID>/SYS/global/sapcontrol/snapshots/fullsysteminfodump_SMH_SM1_solman_2019_07_22_11_13_07.zip
—– 2019-07-22 16:43:07 Exporting runtime dump information —–
No NameServer RTE dump to be created (service not running in a tenant database)
No Preprocessor RTE dump to be created (service not running in a tenant database)
No ScriptServer RTE dump to be created (service not running in a tenant database)
No CacheServer RTE dump to be created (service not running in a tenant database)
No StatisticsServer RTE dump to be created (service not running in a tenant database)
No running XSEngine found on landscape
No CompileServer RTE dump to be created (service not running in a tenant database)
No DPServer RTE dump to be created (service not running in a tenant database)
No WebDispatcher RTE dump to be created (service not running in a tenant database)
No running DIServer found on landscape
Collecting runtime dump for IndexServer on host solman:31046 …
section 0/32 done:
section 0/32 done: BUILD – Build information
section 2/32 done: MODULES – Loaded modules
section 3/32 done:
section 3/32 done: STACK_SHORT – Short call stacks and pending exceptions of all threads
section 4/32 done: CPUINFO – CPU info
section 5/32 done: MEMMAP – Memory map
section 6/32 done: LIMITS – Limits
section 8/32 done: SCHEDINFO – Scheduling information
section 11/32 done: STATISTICS – Statistics data
section 12/32 done: PROCESS_INFO – Process Info
section 13/32 done: XSENGINE – XS Engine
section 14/32 done: JAVASCRIPT – JavaScript stack
section 16/32 done: INDEXMANAGER_WAITGRAPH – Wait graph for index handles
section 17/32 done: INDEXMANAGER_STATE – IndexManager internal state
section 19/32 done: PRE_RESTART_SWVERSION – Software version stored in savepoint the persistency restarted from and with which it was created
section 20/32 done: SAVEPOINT_SHAREDLOCK_OWNERS – Owners of shared SavepointLocks
section 22/32 done: THREADS – Running threads
section 25/32 done: REGISTERED_STACK_OBJECTS – Objects on stack registered to be dumped
section 26/32 done: SYMBOL_CACHE – symbol cache statistics
section 27/32 done: IPMM_MEMORY – IPMM information
section 28/32 done: MEMORY_ACCOUNTING – Memory accounting
section 29/32 done: IMPLICIT_MEMORY_BOOKING – Status of implicit memory booking of the current thread
section 30/32 done: OS_MEMORY – Operating system information about memory
done.
System information written to file /usr/sap/SMH/SYS/global/sapcontrol/snapshots/fullsysteminfodump_SMH_SM1_solman_2019_07_22_11_13_07.zip
Full System Info Dump done.
fullsysteminfodump_SMH_SM1_solman_2019_07_22_11_13_07.zip
[OK]
This will create a runtimedump for the host . runtime dump file will be under traces directory with naming like ‘indexserver….rtedump.trc’.
Refer SAP Note : 1813020 – How to generate a runtime dump on SAP HANA for more details.