HANA Allocation Limit error

[#1]

Hello community,

I have encountered a strange issue.

I have a procedure which is called by a job with a crontrigger. This job fails almost every time because memory allocation limit. But if I invoke the procedure manually it's working perfectly fine every time.

When I look into the performance monitor there is no sign that the memory allocation limit is reached. Maybe I'm reading it the wrong way, but I think it should be ok.

What could be the matter?

Thanks in advance

BR

Jo

[Former Member]

Are you seeing an OOM dump in the DB?

[former_member460045]

Hello Michael,

I had a few dumps because OOM but for the jobs that failed the last 12 hours there is no dump file created/dumps noted.

[Former Member]

I would guess that is because your config is set to generate only one OOM dump every 12 or so hours.

Can you upload the last OOM you saw when the procedure ran and failed.

[former_member460045]

The error occuring is:

• Application Error: SQL exception 2048: column store error: "Schema"."Path::Procedure": line 13 col 3 (at pos 379): [2048] (range 3): column store error: search table error: [9] Memory allocation failed at /sapmnt/ld7272/a/HDB/jenkins_prod/workspace/8uyiojyvla/s/ptime/session/eapi/jdbc/ExternalStatement.cc:912

[Former Member]

I should have been more specific.

Go to your HANA Studio > Traces > Find the relevant indexserver.oom dump that occurred at the same time as the procedure failed.

Upload it here:

https://mdocs.sap.com/mcm/public/v1/open?shr=N6r0Af2Fe_raO8MD2ssTlJ8a_jXbXmXPG8KApNu6UmA

Or better again, generate a full system dump from HANA and upload to the above link.

[former_member460045]

Hello Michael,

I uploaded the file, thanks for your help.

How can I generate a full system dump?

[Former Member]

Searching google I found:

https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.02/en-US/532af53777d0451a9ddb1d152b...

https://launchpad.support.sap.com/#/notes/0001732157

[former_member460045]

Yes it is.

I'm irritated because calling this manually works perfectly fine. How is this possible?

Thanks for your detailled answers.

[Former Member]

My guess would be the way the procedure is written/optimised, so as I suggested, addthe HINT above to the procedure and check if this reduces the consumption.