SAP 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

[former_member230898]

Hello Umakanth ,

The below note is relevant to your issue .

SAP KBA "2069568 - BI Java OOM dumps caused by export operations" regarding this issue.

Also , check the below Note and follow all the suggestion for out of Memory issues.

1515139 - Frequent WEB AS JAVA out of memory crashes and/or core dumps due to large BI data access queries.

let me know if this helps .

Regards,

Bhaskar

[former_member186696]

Hi Uma...

Looks like an export is causing an OOM.

My recommendation to solve this is setup the safety belt parameters.

Follow the steps prescribed in the note 1127156 and set the safety belt parameters for export and result set in the application. The "safety belt" can be activated for a specific Query View or globally

using a parameter in the customizing table RSADMIN.

Execute the program SAP_RSADMIN_MAINTAIN (in transaction SE38) and create the parameter OBJECT = BICS_DA_RESULT_SET_LIMIT_DEF (or BICS_DA_RESULT_SET_LIMIT_MAX) with the value VALUE = <maximumnumber of cells in the result set>.

The recommended setting is 500,000 cells

Also, do ensure that the limits for XLS and PDF (described in the note 1622134), are also set as specified below:

BICS_DA_RESULT_SET_LIMIT_XLS=500000 (for the export to Excel)

BICS_DA_RESULT_SET_LIMIT_PDF=500000 (for the export to PDF)

Kindly bear in mind that the admin parameters will have effect, only when the code shipped with the patch as in note 1622134 is available otherwise no improvement can be seen.

Best Regards,
Edward John
SAP AGS

[Former Member]

Hi Edward John,

Thanks for your input. Apart from applying patch is there any alternate way by increasing JAVA heap memory or any parameters size.Please suggest.

Thanks and Regards,

Uma

[former_member186696]

Hi Uma,

But it was exactly what I mentioned, implement the safety belt parameters.

You can also consider to increase the heap memory.

More details about heap, you can find into these two notes:

1807211 - Spend report triggers out of memory error causing Java server process to restart

1913710 - BI Java Memory Improvements for NW 7.30

But basically, the parameters mentioned previously should solve the issue and are quite simple to implement. You have just to confirm if you are on a BI Java patch where these parameters are considered (probably you are, since the introduction of these parameters are from 2011).

Best Regards,
Edward John

SAP AGS

[Former Member]

Hi Edward,

Thanks for your input.The above solution is just a patch implementation and which restricts the export to excel parameters.With this JAVA patch implementation is there any effect in the existing functionality (patch may contain many features) and also at the same time do we need to go update ABAP patch or JAVA patch is enough?

Thanks and Regards,

Uma