SAP Netweaver Business Intelligence BI / BW

Symptom
You experience a high memory consumption of the TREXIndexserver or the TREXRfcServer on one or more blades that leads to the use of swap space.
Other terms
swapping, overload, BWA, BIA, Accelerator, memory, outage
Reason and Prerequisites
You have loaded too much data into the BW accelerator. In this case, the memory consumption should decrease once you take load off BWA.The limits for parallel query executions are set too high or not set at all. In this case, the memory consumption should decrease once you take load off BWA.The limits for (temporary) query results are set too high or not set at all. In this case, the memory consumption should decrease once you take load off BWA.There is a memory leak in your BWA revision. This is normally indicated by the fact that the high memory consumption does not decrease after you take load off BWA.Solution
Check whether the high memory consumption results from incorrect BWA sizing according to SAP Note 1093719. If your number of indexed InfoCubes exceeds the sizing guidelines, you should either add more blades or remove some cubes from BWA.If you suspect that the high memory consumption results from a large number of parallel users, see SAP Note 1239301 for possible query limitations and adapt the relevant parameters.If you suspect that specific query results lead to high memory consumption, see SAP Note 1315278 for the limitation of query results and adapt the relevant parameters.If none of the above help reducing the high memory consumption, you should upgrade to the latest BWA revision to profit from possible fixes in memory management.
Note: Please check related notes for known memory issues.