BI Publisher issue ends with java.lang.outOfMemory error

BI Publisher issue ends with java.lang.outOfMemory error  tmp file keeps extending upto around 30 MB even though program end with warning before than. i.e. tmp file keep extending after java.lang.outofmemory error.

  

Solution:

1.       Configure the Output Post Processor's JVM. These steps set the JVM to 2GB, depending upon

your server's size you might find 3 GB (-mx3072m), 4GB (-mx4096m) or even 5GB (-mx5120m) is a better value. This setting prevents the error "java.lang.OutOfMemoryError: Java heap space" in the Output Post Processor's log associated to the Subledger Accounting Program.

Login to SQL*Plus as APPS.

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'); 

Bounce the concurrent managers

2.       Increase the number of Output Post Processor as follows:

Logon to Applications with "System Administrator" responsibility 

Navigate to Concurrent -> Manager -> Define

Query for "Output Post Processor" 

Click on "Work Shifts" and Increase the number of processes. 

(If you have 2 processes then make them 4).

3.       1. Go to the XML Publisher Administrator responsibility.

2. Go to the Administration TAB

3. Set the three fields in the Admin page:

Under General -

Temporary directory : set the temporary directory to a large existing writable directory on the concurrent manager tier : Directory should have atleast 20 Gb free space. Set that directory name as temporary directory.

Under FO Processing -

Use XML Publisher's XSLT processor - True

Enable scalable feature of XSLT processor - NULL

Enable XSLT runtime optimization - True

4. Navigate to System Administrator => Profile => System => Query for the below profile and set the value at site level which is enough to complete the requests. (Input is in seconds)

Concurrent:OPP Process Timeout

5. Bounce the concurrent managers

4.       check the OPP Timeout must be set greater than 30min long (to include larger

XML data)

"Concurrent:OPP Process Timeout"

"Concurrent:OPP Response Timeout".

Change the both the values to big values like 10800.

Normally they would be in hundreds.

Please change them at site level. Then only they will reflect

References:

 BUG 8905212 - XML REPORT ENDS WITH JAVA.LANG.OUTOFMEMORY ERROR

XML/BI Publisher Reports Generating "java.lang.OutOfMemoryError" and OPP Logfile Shows "Check that the heap size per Output Post-processor service process is Sufficient" After Submitting Many Jobs [ID 371303.1]

Output Post Processor Fails Due To java.lang.OutOfMemoryError: ZIP002:OutOfMemoryError, MEM_ERROR in deflate_init2