Scribd
Upload
7 views

1860872 - Report not executable in BEx Analyzer 7x - Client out of Memory

The document addresses memory issues encountered in BEx Analyzer 7x when executing large queries or workbooks, leading to various error messages such as 'Client out of Memory'. It explains that the limitations are due to the .NET framework's maximum memory allocation of 1.2 GB for 32-bit applications, which affects data extraction capabilities. The document provides resolutions, including applying specific SAP notes and optimizing workbook settings to mitigate memory consumption issues.

Uploaded by

sandeepfromooty
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
7 views

1860872 - Report not executable in BEx Analyzer 7x - Client out of Memory

The document addresses memory issues encountered in BEx Analyzer 7x when executing large queries or workbooks, leading to various error messages such as 'Client out of Memory'. It explains that the limitations are due to the .NET framework's maximum memory allocation of 1.2 GB for 32-bit applications, which affects data extraction capabilities. The document provides resolutions, including applying specific SAP notes and optimizing workbook settings to mitigate memory consumption issues.

Uploaded by

sandeepfromooty
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

2022-04-01 1860872

1860872 - Report not executable in BEx Analyzer 7x /


Client out of Memory
Version 16 Type SAP Knowledge Base Article
Language English Master Language English
Release Status Released to Customer Category Problem
Component BW-BEX-ET-WB-7X (7.x Analyzer Frontend)Released On 17.02.2022

Please find the original document at https://launchpad.support.sap.com/#/notes/1860872

Symptom

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to
real data is purely coincidental."

• You execute a large query or workbook in BEx Analyzer 7x.


• The execution dumps with one of the following error messages and disconnects from BW Server.
• Error messages:
• Client out of Memory
• Critical Program Error
• No roll storage space of length ... available for internal storage. Table blocks.
• A critical program error has occurred
• CALL_FUNCTION_SEND_ERROR
• CM_NO_DATA_RECEIVED
• System exception thrown while marshaling RFCTYPE_INT to .NET type
• Client-Speicher nicht ausreichend
• Ein schwerwiegender Programmfehler is aufgetreten. Das Programm wird jetzt beendet.
• Too much data for export
• EXPORT_TOO_MUCH_DATA
• If you execute the query/workbook with a finer selection, then the error does not occur.

Environment

SAP NetWeaver All versions

Reproducing the Issue

1. Start BEx Analyzer 7x.


2. Open a large query or open a large workbook and refresh it.

Cause

Why the memory problem occurs:

• The BEx Analyzer 7x is not a tool for the mass extraction of data, but a viewer/navigator tool for data.
• The BEx Analyzer 7x is based on .NET framework 32 bits
• Regardless of the memory capacity in the computer, .NET framework can allocate a maximum of
approximately 1.2 gigabytes (GB) for 32 bit application. All application (running on 32 bit) using .NET
framework uses maximum 1.2 gigabytes (GB) together.
• If excel is the only application using .NET framework on a client PC, then this corresponds to
approximately 750.000 data cells that can be displayed. The limit of 750.000 cells is based on standard

© 2022 SAP SE or an SAP affiliate company. All rights reserved 1 of 4


2022-04-01 1860872

text-size in the cell. The issue may occur earlier (e.g. 740.000 cells) or later (e.g. 850.000 cells).
• When you try to allocate more memory, the system generates an error message and disconnects from
backend system.
• SAP cannot change the .NET framework in BEx Analyzer 7x, thus this limitation will remain. No change
regarding the use of 32 bit is planned in BEx Analyzer 7x.
• Please review SAP note 1040454 to get information about frontend memory requirement of the BEx
Analyzer 7x.

Why this issue does not happens in BEx Analyzer 3x.

• The BEx Analyzer 3x is not based on .NET framework, therefore this limitation does not exist here.

Why this issue does not happens in RSRT.

• The Tx RSRT does not use .NET framework and further RSRT reads/shows only a small part of the
query resultset, not the complete query resultset.

Resolution

We are consistently improving the memory consumption by BExAnalyzer 7x. Please apply all the the
following notes related to this issue.
To get the latest Frontend patch and find the detail installation steps see page:
https://wiki.scn.sap.com/wiki/x/jYibIg

Doing in backend /
Issue Note Frontend optimization included in Frontend patch
additional information
1 Performance 2041337 SAP GUI 730 FEP600 or higher Correction Code: Apply the
in ABAP correction using Tx
Serialization SNOTE or apply the
of Structure Support-Package
Members mentioned in the note.
and Cells Manual Steps: Add
RS_FRONTEND_INIT
parameter
ANA_SERIALIZE_PARTS
with value 'X' in transaction
RS_FRONTEND_INIT.
2 Client out of 2201034 SAP GUI 730 FEP920 or higher SAP GUI 740 Manual Steps: Apply
Memory FEP400 or higher manual change mentioned
Error in the note or apply the
appears Support-Package
after an mentioned in the note.
upgrade to
BW Release
7.40
3 Out of 2193155 SAP GUI 740 FEP401 or higher Front End manual steps:
memory Since Frontend patch
exception FEP401 you find a new
occurs while option "Optimize for large
refreshing a Workbook" in the
workbook workbook settings. Please
with many select this option and save

© 2022 SAP SE or an SAP affiliate company. All rights reserved 2 of 4


2022-04-01 1860872
data the workbook. In case you
providers are not able to open the
due to very workbook settings dialog
large size of due to an out of memory
XML. error, please set the flag
ANA_DESIGNMODE_OPT
before opening the
workbook to avoid the
refresh function when
going to design mode and
loading the workbook
settings dialog. It is
recommended to close an
existing huge workbook
before opening another
huge workbook in the
same session. Or you
open it in a different
session to avoid out of
memory issue.

How many data cell is involved?

1. Execute the query in Tx RSRT2.


2. Count the columns and rows:
3. Calculate the number of cells.
(The example above shows: 5 columns x 30 rows = 150 cells.)

How to reduce the amount of data cell being displayed?

• ... for using BEx Analyzer 7x:


• Reduce the number of Grid Items / Data Provider in the workbook.
• Reduce the number of characteristics / attributes / key figures in drill.
• Use additional filter / variables to reduce the amount of data to be displayed.
• Switch optional variables to mandatory variables to force user to make a selection.
• Use Conditions.
• Switch on the Zero-Suppression.
• Suppress the result rows.

How to avoid the error message ONLY?

• You can use the safety belt (see SAP note 1973478) with less than 750.000 data cells to only avoid the
error message. The limitation of 750.000 data cells still applies.

How to extract large data set?

• In our experience customers require huge grid for further calculation/aggregation. Then here customer
are NOT looking for reporting tool but rather an extraction tool. You need to do your own research to
find which tool is the best fit for your requirement.
• Some hints which can help you for extraction:
1. Use of APD with limitation, see SAP notes 794257 and 751577 and online documentation:
Activities in the Analysis Process Designer (APD).
2. Queries as Info Providers for open-hub (BW730 SP8 onwards), see online documentation:
Distributing Data from the BW System.

© 2022 SAP SE or an SAP affiliate company. All rights reserved 3 of 4


2022-04-01 1860872

Conclusion:

If the issue remains using all the parameter and ABAP correction mentioned above with SAP GUI 730
Frontend patch FEP920 or SAP GUI 740 Frontend patch FEP400 or higher, this issue will be finally
categorised as limitation of .NET Framework (1.2 GB) in 32 bit application (Excel / Microsoft office) as already
mentioned in note 1040454. This limitation could be overcome using 64 bit application (excel /Micorsoft
office) but BExAnalyzer does not support 64 bit Excel. SAP offers BusinessObjects Analysis, edition for
Microsoft Office 64Bit Version (64Bit OS + 64Bit Office + 64Bit AO) to overcome the limitation of .NET
Framework (1.2 GB) in 32 bit application. Please review SAP note 1729141.

Keywords

BEx Analyzer, out of memory, outofmemory, Critical Program Error

Products

SAP NetWeaver all versions

Terms of use | Copyright | Trademark | Legal Disclosure | Privacy

© 2022 SAP SE or an SAP affiliate company. All rights reserved 4 of 4

You might also like