Memory allocation failed error

[rindia]

Hi,

I am running the SQL in SQL console (HANA revision 58). After 2 minutes, I am getting the error:

SAP DBTech JDBC: [2048]: column store error: search table error:  [9] Memory allocation failed.

The query is based on joining many HANA tables and views (non-materialized) with concatenation columns and some views has huge data volume.

I am looking for solution to execute the query with sufficient memory allocation. Is there any setting required to do so?

Regards

Raj

[rindia · Accepted solution]

Hana revision is upgraded to 62 (on the week end) and it is strange that I am not getting this error any more. Also I not changed anything.

Regards

Raj

[Former Member · Accepted solution]

Hi,

I am a newbie. I am facing this issue in Rev 74. Please help!

In my case, I cannot add filters to restrict the data. Actually I saw some SAP video in which SAP is mentioning like they are processing billions of data in HANA. But, We have data in Millions and facing this error.

"Error executing the query
Error: SAP DBTech JDBC: [2048]: column store error: search table error: [9] Error executing physical plan: Memory allocation failed; in executor::Executor in cube: _SYS_BIC:Analytical View name/olap"

Appreciate your suggestions!

Thanks in advance!!

Regards,

Jeni

[rindia · Accepted solution]

Hi Jeni,

To me the same problem was resolved when we upgraded. You are in rev 74 and obviously greater than what we upgraded before.

Me too, want to know what the solution can be.

Let us see what others suggest.

Regards

Raj

[Former Member]

HI Everyone,

                    I am facing same error in sap hana studio. how to solve this issues?. please give a solution.

         SAP DBTech JDBC: [2048]: column store error: search table error:  [9] Memory allocation failed.

[Former Member]

Hello Rajesh,

1. Please don't resurrect old threads. Open a new one with your problem.

2. Please provide at least the minimum information such as:

2.1 Your HDB revision

2.2 Your sizing information (namely how much memory you have)

2.3 What you are doing which is obviously causing the OOM

The above said, have a look in your trace files and you will see what is potentially causing the OOM.

KR,

Amerjit

[Former Member]

This message was moderated.

[Former Member]

This message was moderated.

[Former Member]

This message was moderated.

[Mushfiq]

This message was moderated.

[former_member182114]

Hi Raj,

Depending on your views will be necessary use variables / parameters to filter on lowest level of data.

If you are conducting development you have also an option to hard code these filters on biggest tables of your model.

Anyhow, this is a thing you must investigate as there's a possibility of your views are avoiding push down of selection filters.

No enough information to judge.

Regards, Fernando Da Rós

[rindia]

Hi Fernado,

I am on support and not in development.

Regards

Raj

[former_member184768]

Hi Raj,

I agree with Fernando. Even my first impression of this post was, "not enough information".

I understand you are currently supporting the HANA application, but you may suggest the user to execute the reports with some additional filters.

I think many of the applications developed so far, were initially developed on the early revisions of HANA. Considering that HANA is relatively new development platform, the applications might not have been tuned properly for the performance. Now with high data volume you may face performance issues. But that doesn't mean, you cannot change the existing application with some Change Request.

As part of the support team, you can perform basic analysis with the query plan and identify the bottlenecks. You are among the very active member on this forum and quite experienced on HANA, . So I don't need to mention here how the basic analysis should be done.

As Fernando mentioned, I think the filters should be pushed down to reduce the result set generated. Unless the intermediate result set and data transfer between the engines is reduced, it would be difficult to get good performance or even query execution on HANA.

You already know quite many things on how to achieve it and I am sure you will figure that out.

Regards,

Ravi

[hugo_amo]

Hi Raj,

Could you check this KBA? It might help.

1862506 - HANA: Statisticsserver runs out of memory (OOM) after after SPS05

Regards,

Hugo

[rindia]

Thanks Amo.

I am waiting for the approval to change the settings.

Will update once I get the approval.

Regards

Raj

[hugo_amo]

Keep us updated,

Regards,

Hugo