1967896 - Basic recipe for troubleshooting memory problems with Bex queries (Information for support)

A Bex query terminates with a memory related dump such as TSV_NEW_PAGE_ALLOC_FAILED, STORAGE_PARAMETERS_WRONG_SET or SYSTEM_NO_ROLL.

When facing memory problems in BEx queries, the main problem is that more data is requested than the current memory configuration allows.

In some, rather rare cases, SAP BW development can optimize the processing of Bex queries because the data is requested in a suboptimal way.

Your initial analysis and SAP support's analysis will require the following ingredients:

1) Ingredients for analysis:
  1a) Memory required at the time of the dump and current memory configuration 
  1b) Technical ID of the query, Steps to replicate the dump
  1c) Number of records/cells expected for this query
  1d) Reduced query and Bex statistics
  1e) List of memory intensive features the query is using

For further analysis directions are required:

2) Directions for analysis

If the use of mass data cannot be avoided, you need:

3) Alternatives and Workarounds

• SAP Netweaver - All Versions
• SAP BW/4HANA - All Versions

KBA , BW-BEX-OT , OLAP Technology , BW-BEX-ET , Enduser Technology , BW-BEX-OT-OLAP , Analyzing Data , BW4-AE-CORE , Core Services , How To