Troubleshooting XML Publisher Out of memory Error

When an BI Publisher report completes with Out of memory issue it can be at 2 Levels.
XML Data generation
Report Generation from XML data.
This Document will cover the Solutions for below Program errors in the Log file.

‘****Warning!!! Due to high volume of data, got out of memory exception…***
‘****Please retry with scalable option or modify the Data template to run in scalable mode…***
OR
java.lang.OutOfMemoryError: Java heap space

XML Data Generation :
Increase the memory of Concurrent Program Definition as below:
Navigate to System Administrator > Concurrent > Program > Define.
Query for the Failed Concurrent Program
Set the Options field to “-Xmx2048M” (Note: Do not miss the dash before the X)
Save
Bouncing the Concurrent Manager is optional.

Run the report with ScalableFlag as “Y” and Debugflag as “Y” with Step1 in place.
Steps to Setup ScalableFlag
Navigate to System Administrator > Concurrent > Program > Define.
Query for the Failed Concurrent Program.
Click on parameters.
Add a new Parameter with Below values.

Parameter	P_SCALABLE_FLAG
Description	ScalableFlag
Enabled	Check
Default Type	Constant
Default Value	Yes
Prompt	P_SCALABLE_FLAG
Token	ScalableFlag

Steps to Setup Debugflag
Navigate to System Administrator > Concurrent > Program > Define.
Query for the Failed Concurrent Program.
Click on parameters.
Add a new Parameter with Below values.

Parameter	P_DEBUG_FLAG
Description	DebugFlag
Enabled	Check
Default Type	Constant
Default Value	Yes
Prompt	P_DEBUG_FLAG
Token	DebugFlag

When we run the report again with newly added parameters the log should show the below.
Report SQL.
It should show Calling XDO Data Engine and Scalable Mode on.

Report Generation from XML data

If XML Generation is Fine and OPP fails with “java.lang.OutOfMemoryError” Exception.
Change the Following values from XML Publisher Administrator.

Responsibility=>Administration UI

General => Temporary directory => \tmp
This could be any directory with full read and write access

FO Processing=>
Use XML Publisher’s XSLT processor =>true
Enable scalable feature of XSLT processor=> true
Enable XSLT runtime optimization=>true

Check the Heap size of OPP JVM.

SQL> select DEVELOPER_PARAMETERS
from FND_CP_SERVICES
where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME = ‘FNDCPOPP’

DEVELOPER_PARAMETERS
+—————————————————–+
J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m
Set the JVM Heap size using following SQL query
SQL> update FND_CP_SERVICES
set DEVELOPER_PARAMETERS = ‘J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx2048m’
where SERVICE_ID =
(select MANAGER_TYPE
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME = ‘FNDCPOPP’);

SQL>Commit;

Nikethan Reddy