Error executing physical plan: aggregation: not enough memory

[Former Member]

Hi Everyone,

I am getting error dumps while executing a report based on an Infocube using BIA.

This is the first time we are facing this error, could any body please suggest the possible solutions to resolve this error.

Thanks and regards,

Sonal Patel.

[former_member220624 · Accepted solution]

Hi Sonal,

You need to contact your Basis team for this issue.

Plesse send them the details along with the dump.

I had this issue in my project and it was solved by basis team.

Regards,

Amit

[Former Member · Accepted solution]

Hi Amit,

We have already conveyed this issue to basis team but did not find any permanant solution.

Could you please share the solution provided by your basis team to resolve this issue ?

Regards,

Sonal Patel

[former_member220624 · Accepted solution]

Hi Sonal,

Please try to activate and fill the BIA for the cube once again and check the job in SM37.

In case it throws a dump or an error message,please forward the same to your basis team.

Regards,

Amit

[sundeep_chalasani]

Hi Sonal,

The error is due to the cell limit restriction on the BWA (40 million cells by default). Not necessary the cells you are trying to output in your BEx query but the cells created in the internal table when you are trying to read from the BWA memory.

The below note should solve your issue. If you are familiar with theTREXAdmin Python tool, you can do it yourself but if not kindly forward the below note to your BASIS team.

1740610 - BWA 7.00 and 7.20: Using dynamic max_cells_one_index

Thanks and hope it solves your issue

Sundeep

[Former Member]

We suffered a similar problem in the recent past. What we discovered was that one of the blades in our BWA had a problem with its mirror disk. This apparently was causing indexing data to corrupt more quickly and bring the array out of balance. Complete re-indexing of the infocubes and running of the landscape reorganizing job would temporarily fix the issue, but the situation would appear again in a few days. After taking care of the hardware issue and doing a complete delete and rebuild of all indexes took care of the problem. Now, also consider the possibility that the particular cube triggering the problem has grown too big, exceeding the capability of the BWA hardware to contain it. If that is the case, you will probably start seeing "BWA Overloaded" messages from the monitor (RSDDBIAMON). In that case, consider eliminating some of the data in the cube or resize the BIA to properly increase resources.

Regards