on 10-13-2010 3:05 PM
Hi Guys,
I have BEx 7.0 Analyzer, I am trying to run nearly 55k lines of query with 34 column.
I get an error message client out of memory. If i run the same in rsrt and web analyzer it works fine.
Is there a way to increase the BEx analyzer memory or BEx analyzer is limited to number of cells?
I am using excel 2007.
If I remove 10 columns from the query it works fine, I think this is due to the number of cells restriction.
Is there any way to fix this issue?
Regards,
Anand
Will SAP or microsoft solve the root cause??
It's needed to be solved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gang,
See 1040454 - Front-end memory requirement of the BEx Analyzer
http://service.sap.com/sap/support/notes/1040454
Regardless of the memory capacity in the front-end, a process can allocate a maximum of approximately 1.2 gigabytes (GB) in the .NET framework.
This corresponds to approximately 750,000 data cells that can be displayed.
When you try to allocate more memory, the system generates an error message ("Client Out of Memory", for example). In this case, reduce the number of cells to be displayed.
This is a Microsoft limitation, not an SAP limitation.
John Hawk
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I am also dealing with same issue, anyone got solution to this problem ?.
Thanks
Nilesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Solved
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Everyone,
I am also running into a similar issue with 7.0 and Excel 2007. I just wanted to comment regarding the 750,000 cell limitation with .NET framework. I'm currently running a query that returns 76,828 rows and 14 total columns (including key and text fields for some attributes) succesfully. It may be possible that our Basis team has changed some setting for us but i don't believe 750,000 is the Maximum.
~Troy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anand,
Your file is a big file, its very common to get such kind of issues.
You can check with the basis team to increase the memory allocated on server for running the queries but i dont foresee it being of much more use.
Its better to restrict/ remove few coloumns.
Please close the thread if you feel the question is answered. Keep the Forum clean.
Regards,
Den
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Akashdeep.
Let me check with excel 2003. But another problem is currently i am running the query till august month, which is of 53K.
At the end of this year the record will sure cross 65K, thats why I went for upgrade from Excel 2003 to Excel 2007.
I think SAP BEx cannot execute huge volume of data. This is something were SAP BI tool need to improve.
Because I have seen more people has come across with this issue. But I did not find any solution anywhere.
I am keeping this thread open for while, let me see anyone can get me solution.
Regards,
Anand.
Hi,
This is memory issue. Please see the OSS note 1040454. The maximum memory for front end processor = 1.2 GB. To find the memory used use the formula
mem = 100MB + (#rows x #columns) x 0.0016 MB
Regardless of the memory capacity in the front-end, a process can allocate a maximum of approximately 1.2 gigabytes (GB) in the .NET framework.
This corresponds to approximately 750,000 data cells that can be displayed.
The system issues an error message when you try to allocate more memory. In this case, reduce the number of cells to be displayed.
Regards,
Raghavendra.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.