HANA Index server Crash due to HEX Engine Not able to Handle OOM on HANA2.0 Rev 36/37.02

Issue :

HANA Index Server crash due to HEX engine not able to Handle OOM.

Analysis and Solution:

Though the HANA Memory usage was never crossed 50% still Index Server crashed and Trace files did not provide the exact cause of the crash. There was no OOM Dump Generated.

The crash dump provided the information that a SIGNAL 6 was caught which means abortion. And the call stack showed our HEX engine responsible for not being able to handle the OOM exception that occurred.

We identified one HEX engine function/method that can cause the abortion and crash the index server in case it will trigger the OOM. But since in this function/method our HEX engine does not really allocate much memory need for the transaction (max. only a few bytes). Below is the snippet of Crash Dump.

0: raise + 0x2b

1: _crashImpl(char const*, int, char const*, ltt::exception const*) + 0x17a

2: Basis::crashImpl(char const*, int, ltt::exception const&) + 0xe

3: Basis::DefaultCrashHandlers::unhandled_exception(ltt::exception const&) + 0x45

2779784 - SAP HANA 2.0 SPS 04 Database Revision 041 : Note says the above issues has been fixed with the SPS 04 and Revision 041.

In revision 36 it has this weakness of handling OOM's for a specific HEX engine function. There was no change around that HEX codeine between 36 and rev. 37.02

On SPS04 HEX engine is capable to handle OOM situation and will not crash. This issue has been fixed with Revision 041.