TSV_TNEW_OCCURS_NO_ROLL_MEMORY Dump

Hello SAP Experts,

While executing any query in RSRT the below errors occurs:

Short Dump:

Runtime Error TSV_TNEW_OCCURS_NO_ROLL_MEMORY

Short Text:

No roll storage space of length XXXXX is available

To regenerate the error please do the following:

• First, run t-code RSRT
• Now enter the query technical name or locate the query using the F4 option
• At last, Execute

Please help me to resolve this error.

Cause of the Error: TSV_TNEW_OCCURS_NO_ROLL_MEMORY

This error often occurs because the memory allocated for roll areas- a type of memory used for processing internal tables or user sessions in SAP- isn't enough to contain the quantity of data a query processes. It can be caused by:

• Large Dataset or Inefficient Query Design:

The query gets executed over a large dataset with no proper filters or data aggregation, which results in high memory usage.

• Below Average Memory Configuration:

The SAP system's memory specifications, including those for roll memory (ztta/roll_area, z.t.a).jpeg is too small to handle the workload.

• Exhaustion of Available Resources:

The system's overall memory (roll area, heap memory, or extended memory) is heavily utilized by other processes, leaving insufficient memory for the query execution.

• Poorly Designed Data Source:

Poorly built database tables or InfoCubes supporting the query could result in ineffective processing or high memory requirements.

Solution:

1. Analyze the Short Dump

• Use T-code ST22 to view the detailed short dump. Look for:
  • The program or report causing the error.
  • The exact memory demand (size in bytes).
  • Recommendations or traces are provided in the dump.

2. Optimize the Query

• Refine Filters: Reduce the dataset by applying specific filters.
• Limit Output Rows: Adjust the settings to retrieve fewer rows.
• Simplify Calculations: Remove complex logic or aggregations within the query.

3. Adjust Memory Parameters

• Increase the memory settings related to roll areas:
  • ztta/roll_area: Defines the size of the roll area per user.
  • ztta/roll_extension: Governs the size of the extended roll area.
  • em/initial_size_MB: Adjusts the extended memory available.
• Work with the BASIS team to update these parameters in the Instance Profile and restart the system for changes to occur.

4. Monitor System Performance

• Use T-code ST02 to check SAP memory use and make sure roll memory utilization is within permissible limits.
• Find other processes that occupy a large amount of memory which could subsequently be optimized or rescheduled.

5. Optimize the Data Source

• Analyze the InfoCube or tables used in the query:
  • Remove unnecessary dimensions or measures.
  • Ensure indexes are created and used effectively.
• Perform a database statistics update to help the query optimizer choose efficient execution paths.

6. Use Aggregates or Partitioning

• If InfoCube processes large datasets, consider creating aggregates or partitioning data to distribute memory usage more efficiently.

7. Test After Changes

• Re-run the query in RSRT after making adjustments for memory usage optimization, and also monitor the improvement in terms of memory usage and performance.