cancel
Showing results for 
Search instead for 
Did you mean: 

SAP BW Server running out of Memory when BO reports are Scheduled

Former Member
0 Kudos

Hi All,

We have a situation where whenever any user is scheduling/executing any of business object report, all the memory of our SAP BW system is used up and if the BO instance is not killed it crashes the server. More facts explaining the scenario and landscape:

- We are on BO 4.0 and BW 7.3

- Reporting Front end is BO and Data source is always SAP BW.

- BO report execution is via user bo-rpt which accesses SAP BW system in dialog process (In this way uses all the memory

from the system).

- SAP BW system has 33 GB of Memory which is completely exhausted when report runs for sometime.

- Report usually extracts around 1 year of data from SAP BW.

Any help or suggestions are most welcome.

Best Regards

Ritesh Singh

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi All,

I will try to answer all your questions:

- We are on BO 4.0 SP2 Patch level 6

- Both CR and WebI reports are scheduled/executed

- Connection type is mainly .unx but direct bex queries are also used

- Some reports have 15-20 rows and some have more than 100.

- Underlying Bex queries when executed in BW system run absolutely fine.

- Problem is only when any large report is scheduled in BO (It almost blows up the memory)

- System lanscape is fine and the Disc space and Memory are ample to support the system

Let me know if any more answers are required from my end.

Best regards

Ritesh Singh

Derek_Fox
Contributor
0 Kudos

Hi Ritesh

I see you are on BI 4.0 SP2 Patch Level 6, therefore I would suggest applying the lastest patch for BI 4.0 SP2 (latest is Patch Level 12) as there was a lot of changes and corrections made between patch 6 and 10.

Regards

Derek

Former Member
0 Kudos

Hi,

Try and isolate if there is a particular report that causes the issue and then have a look at the underlying BEx query. You can also monitor the reports from SM50. You may just have a BEx query that needs to be optimized.

Thanks,

John

Former Member
0 Kudos

Hi All,

Sorry for the substantial delay in posting a reply. The issue was resolved a long time back. Measures taken :

- A number (10-12) of BO reports were scheduled to run in parallel. Rescheduled all of them to run one after another.

- Ensured not more than 4 BO reports are executing in parallel.

- One of the BO reports was optimized for better performance.

Best Regards

Ritesh Singh

Answers (3)

Answers (3)

Former Member
0 Kudos

Ritiesh

BW - 33GB should be decent for BW system

1), Make sure BW SAP parameters are tunes as per OLAP SAP recommendations.

2). Make sure DB parameters are tuned as per SAP recommendation.

Check below note for SAP BW parameters - 192658 Setting parameters for BW systems

BO -

Tune the tomcat parameters - Refer to below note

1346684 - "java.lang.OutOfMemoryError: Java heap space" in Tomcat Web Application Server

1186554 - How to tune Tomcat to serve client requests faster

1186474 - Tuning Tomcat for frequent Internal Server Errors, blank pages in Application Foundation, AcceptEx errors in Apache logs, and slower system performance

Tune parameters as per above recommendation and update the results please...

Derek_Fox
Contributor
0 Kudos

Hi Ritesh

As Sebastian mentioned, without more detailed information it is difficult to provide some answers.

However interpreting your questions that you asked regarding the large memory consumption on the BW system. This is not a BusinessObjects BI issue, but which may be due to a very large dataset been extracted in the BW system from the database and stored in memory to be passed to the BI system.

Extracting 1 year's worth of data technically sounds like a lot of data, I'm guessing that it's line items? How many rows and columns are in the report? There is a formula in an OSS note on the SAP Marketplace that you can use to calculate the memory requirements of the query/report on the BW system.

Another factor which may be causing the system to run out of memory, may be due to a sub-optimal configured BW system. Which involves many aspects, in terms of:

- system landscape design

- hardware installation

- software installation of OS, database and application

- system configuration settings of the OS, database and application

- data model design

- housekeeping/maintenance activities

To resolve the memory consumption on the BW system, the first option is to reduce the number of rows and columns in the query/report to reduce the amount of data required (reduced memory requirements). If this does not resolve the issue, then you'll have kick-off a performance optimization project to try and optimize the BW system. Note: When you optimize a BW system, you have to balance all aspects.

Alternatively, if its the business's requirement to have a large report of 1 years worth of data, then maybe you should be then looking at the SAP HANA system (in memory) instead?

Regards

Derek

0 Kudos

Hi,

which patchlevel do you have on the BI4 side? Which Report kind - CR, WebI, ...? How many rows should the report return? What is the connection type - .UNX, direct BEx? Whats happens when you run the underlaying Query (if it is a Query) native on BW?

Regards

-Seb.