cancel
Showing results for 
Search instead for 
Did you mean: 

SAP HANA (AWS) 'OUT OF MEMORY'

Former Member
0 Kudos

Loading a few million rows into a table. Get :-

Could not execute 'CALL PUBS3.POPULATE_DAILY_SALES_BOOK (36500)'

[129]: transaction rolled back by an internal error:  [129] PUBS3.POPULATE_DAILY_SALES_BOOK: line 39 col 2 (at pos 641): GenericFailure exception: transaction rolled back by an internal error: Out of memory $REASON$

I'm guess this is due to trying to generate 40 millon rows in one transaction.    I guess if I break it up into multiple transactions I'll be OK.

However I'd have thought than HANA had plenty of space in memory for this table.

So my questions are :-

(1)  How can I check what is consuming memory in HANA

(2) Dos HANA attempt to write data out to disk  - i.e. free up memory - so that active transactions will NOT  be rolled back? Is this configurable?

Cheers,

Chris

Accepted Solutions (1)

Accepted Solutions (1)

former_member184768
Active Contributor
0 Kudos

Hi Chris,

On your first question, please find a very nice document by Chaim Bendelac explaining how to find out what is occupying the memory. Please check the HEAP memory, Shared memory and memory in Column store and Row store to identify how the memory is being used.

http://www.saphana.com/docs/DOC-2299/version/1

Coming to the second point, I guess, currently no. I heard that this concept may be coming in the next releases, but currently if the temporary memory / used memory goes over the allocation limit, then the active transaction, requiring additional temporary memory, may crash.

Keeping the transaction smaller may also help, so that the temporary memory is de-allocated from the current transaction and returned back to the pool.

Regards,

Ravi

Former Member
0 Kudos

Ravindra,

thanks for a very helpful reply.

Cheers,

Chris

Answers (1)

Answers (1)

Former Member
0 Kudos

This message was moderated.