cancel
Showing results for 
Search instead for 
Did you mean: 
Subscribe

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

0 Likes
View Entire Topic
Former Member

I looked at the oom dump file.

So the top allocator is consuming 5GBs which is:

Pool/JoinEvaluator/JECreateNTuple

So within your procedure, you could consider setting the hint USE_OLAP_PLAN (SAP Note 2142945) for testing purposes in order to check if a switch from join engine to OLAP engine works and results in a reduced memory consumption.

As a workaround the NO_GROUPING_SIMPLIFICATION hint (SAP Note 2142945) can be used. If triggered by BW / MDX, you can also disable the RSADMIN parameter MDX_F4_USE_SQL (SAP Note 1865554).

Is this the call that you are making at time of the dump:

SQL: Insert Into "SCC"."SCC.Development.model::data.SccData_Union" SELECT * FROM "_SYS_BIC"."SCC.Development.view/CV_SccData_Union_comp"

BR

Michael

former_member460045
Participant

Hello Michael,

I'm writing late, sorry for that, I was pretty much caught in work lately.

I found the error, when I tried to transport the packages. They throw a error that some objects couldn't be activitated. So I looked into it more deeply and it was because of another call that writes a calc view into a table where the output attributes of the cv were in different order than in the table definintion in the hdbdd file.

Now its working like a charm again.

Thanks a lot for your help and valuable inputs.

BR

Jo