Skip to main content

Managing memory usage during extraction

To avoid system slowdowns and instability due to high memory usage during SAP data extraction, you can control the consumption on the application server level or the database level.

Managing memory consumption on the Application Server level

Active SAP processes, including Celonis extractor jobs, consume the application server memory. Here are some profile parameters responsible for managing memory in SAP that you might want to set:

  • abap/heap_area_dia: sets the heap memory limit for dialog work processes.

  • abap/heap_area_nondia: sets the heap memory limit for non-dialog work processes, such as background jobs.

  • abap/heap_area_total: defines the cumulative heap memory limit for all work processes.

  • abap/heaplimit: specifies the maximum private memory allocation for a single work process before it is restarted.

Note

All changes made to SAP memory usage should be consulted with the SAP Basis team.

Managing memory consumption on the database level

Database memory is consumed during the execution of queries by the Celonis Extractor. This can represent a significant load, particularly with large datasets. You can control the memory usage with the following parameter:

  • statement_memory_limit: this parameter restricts the memory allocated to a single SQL statement. This is critical for preventing individual queries from monopolizing database resources, especially in SAP HANA environments.

For more information, see SAP documentation.