HANA 2 Memory Leak after Upgrade

[former_member246431]

Hi,

some weeks ago we upgraded our Solution Manager 7.2 from HANA 1.0 SP12 to HANA 2.0 SP4 Rev 2.

Now we have a memory leak problem on the JAVA System of the SM. (ABAP is fine with same DB Version).

Before the upgrade the system used 30GB Memory. Now the System gathers more and more memory until it allocats all (100GB) and then the errors start, backup fails, due to insufficent memory, ...

On the OS we see that the hdbindexserver is using this memory.

It's only on the JAVA production System. JAVA Development is running fine, with the same DB Version.

Did we miss to set a Parameter ? Or any other suggestions ?

Thanks

Lukas

[dennispadia]

Hello Lukas,

Can you please run "Memory Overview" SQL statement from SAP Note 1969700. It will gives you the list of allocators that are holding memory. Based on that further investigation can be done.

Regards,

Dennis Padia.

[former_member246431]

Hi,

thanks for the answer, attached the Memory Overview. memoryoverview.txt

Hard to see any errors.

Today we updated the DB to Rev 43 in the hope the error is fixed. We will monitor the system and look.

Thanks

Lukas

[dennispadia · Accepted solution]

Hello Lukas,

As you can see HANA heap memory takes around 78 GB of memory and below allocators uses the most.

Pool/RowEngine/QueryExecution/SearchAlloc - 23 GB

Pool/RowEngine/Session - 14 GB

Pool/Statistics - 11 GB

If possible kindly check below SAP Note, as solution manager java uses jdbc connection to connect to java database. Below SAP Note suggest similar symptoms.

2711824 - High Number of Prepared Statements Causing High Usage of Memory Allocator Pool/Statistics

If you have upgrade HANA databases, kindly update HANA client on SolMan JAVA application servers as well to version 2.3.38 (or higher).

Regards,

Dennis Padia

[former_member246431 · Accepted solution]

Hi Dennis,

thanks for the Note. I implemented it yesterday and the memory leak ist gone.

Thanks !

Best regards

Lukas

[former_member464744 · Accepted solution]

Hi Lukas and Dennis,

thanks for posting issue and solution. We had these memory leaks too and implementing snote 2111824 helped.

Best regards

Angelika