Symptom
So many out-of-memory errors are generated even though plenty of memory is available on a system.
The Pool allocators for this OOM messages appears to be random.
Examples:
[103883]{332892}[-1/-1] 2019-10-15 11:23:50.411670 w Memory mmPoolAllocator.cpp(01142) : Out of memory for Pool/ims_search_api, size 521B, alignment=1B, flags 0x0, reason CANCEL_FLAG
[104879]{335561}[73/-1] 2019-10-15 11:27:06.434699 w Memory mmPoolAllocator.cpp(01142) : Out of memory for Pool/malloc/libstdc++.so.6, size 112B, alignment=1B, flags 0x0, reason CANCEL_FLAG
[211381]{350552}[878/7140496925] 2019-10-15 13:56:23.883529 w Memory mmPoolAllocator.cpp(01142) : Out of memory for Pool/TransMgr, size 56B, alignment=16B, flags 0x0, reason CANCEL_FLAG
Read more...
Environment
HANA 2 sps 04
Product
Keywords
reason CANCEL_FLAG, CANCEL_FLAG, OOM, Out of memory, false OOM, false out of memory , KBA , HAN-DB , SAP HANA Database , 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.