OOM issue

[Former Member]

Hi all, We are getting continuous OOM issue in SAP BI server.But we could not anlayze any thing from this dump.Please provide suggestions. +74113 #1.5^H#8A9236AD7B040529000000030084007E00051B87F33AE53B#1437645598811#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#USER#6435##sapXXX_XXX_121154051#USER#9becd4b2311f11e5 84a600000738aa03#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Java###09:59_23/07/15_0002_121154051 +74114 [EXCEPTION] +74115 {0}#1#java.lang.OutOfMemoryError: Java heap space (failed to allocate 635642208 bytes) +74116 at java.lang.StringCoding$CharsetSE.encode(StringCoding.java:336) +74117 at java.lang.StringCoding.encode(StringCoding.java:380) +74118 at java.lang.String.getBytes(String.java:610) +74119 at com.sap.ip.bi.export.office.common.OfficeHtmlDocument.writeOfficeHtmlDocumentToByte(OfficeHtmlDocument.java:253) +74120 at com.sap.ip.bi.export.office.common.OfficeHtmlDocument.writeOfficeHtmlDocumentToByte(OfficeHtmlDocument.java:265) +74121 at com.sap.ip.bi.export.office.impl.excel.MsExcelConverter.getBinaryContent(MsExcelConverter.java:149)

Thanks and Regards,

Uma

[Reagan]

The note suggested by Hemanth is the one to start with.

You mentioned that the system is facing OOM dumps frequently. A quick question. Is the server sized and configured with enough memory for the BI system?

Is this a dual stack or a stand-alone Java stack?

How many server nodes does the Java system have?

What is the heap size assigned for the node(s)?

There is no point in increasing heap parameters when there is lack of physical memory.

The issue is pretty clear in the log you have supplied. The JVM is trying to allocate 600MB and it fails. To fix this issue you need to check if the JVM is updated and the parameter are set correctly.

Additionally based on the log the OOM happens during export operations. You should consider setting the safety belt in the BI system.

Check these notes/KBA.

2069568 - BI Java OOM dumps caused by export operations

1622134 - Safety belt: Results quantity is too large (Excel/PDF)

RB

[Former Member]

Hi Reagan,

Thanks for your input. As per that log it is failing for 600MB. If it is the case JVM memory max is 600 MB ? or it is storing multiple dumps and when it reaches it max and failing.

Could you please let me know what are the PARAMETERS DEFAULT SETTINGS OF JVM.

And also please suggest how to check these parameters(I am BI consultant).

Is the server sized and configured with enough memory for the BI system?

Is this a dual stack or a stand-alone Java stack?

How many server nodes does the Java system have?

What is the heap size assigned for the node(s)?

Thanks and Regards,

Uma

[hemanth2]

For starters, set the heap to 4 GB atleast and try to add a server node if you can. These are all Basis tasks.

[Former Member]

can you check this

1792285 - java.lang.OutOfMemoryError: unable to create new native thread when a high-volume publicat...

[hemanth2]

Hi Uma,
 

Hope you are doing good.

Some steps you can do for optimum usage of services:

1)

Please have a look at SAP Note No. 723909:

***************************************

Remark 2: increasing of the heap size or permanent space is harmless on 64 bit systems (given that enough physical memory is available

***************************************

Increase the heap size if possible.
2)

Make sure that enough threads are configured. Please check the note:1016241 - J2EE Engine hangs because of unsufficient system threads
3)

Also check the below note so that the BI transactions can be

optimized:

SAP Note No. 1515139 - Frequent WEB AS JAVA out of memory crashes and/or

core dumps due to large BI data access queries

Kindly apply all these recommendations and the server behaviour should definitely improve a lot.

If you face the error again, kindly check the below link to generate the heap dump. Please have a look at: SAP Note No. 1004255- How to create a full HPROF heap dump of J2EE Engine

Hope this helps.

_ _ _ _ _ _ _ _ _

Kind Regards,

Hemanth
SAP Active Global Support

_ _ _ _ _ _ _ _ _