Symptom
- In an SAP ASE HADR environment, RMA fails to start or repeatedly terminates after startup.
- The following errors may be observed from RMA crash trace:
***Warning: INFO: os::commit_memory(0x0000xxxxxxx00000, <value>, 0) failed; error='Not enough space' (errno=12)
[M.Ns][warning][os,thread] Failed to start thread "Unknown thread" - pthread_create failed (EAGAIN) for attributes: stacksize: 1024k, guardsize: 0k, detached.
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map <value> bytes for committing reserved memory.. Out of swap space or heap resource limit exceeded (check with limits or ulimit)?
# An error report with more information is generated,[M.Ns][warning][os,thread] Attempt to protect stack guard pages failed (0x0000xxxxxxx00000-0x0000xxxxxxx04000).
[thread PID also had an error (e0000004)
Details: pc=0x0000000000000000 siginfo: <null>] - The operating system shows a low value for /proc/sys/vm/max_map_count , for example:
cat /proc/sys/vm/max_map_count
65530
Read more...
Environment
- SAP Adaptive Server Enterprise (ASE) all versions with Always-on Option (HADR)
- Linux OS
Product
Keywords
RMA, HADR, SAP ASE, max_map_count, memory mapping, Out of memory, RMA startup failure, OOM, crashed, down, crashing, trace , KBA , BC-SYB-REP-SAP , Replication with SAP Suite / SAP BW , BC-SYB-REP , Sybase Replication Server (standalone) , 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.
SAP Knowledge Base Article - Preview