DOYENSYS Knowledge Portal




We Welcome you to visit our DOYENSYS KNOWLEDGE PORTAL : Doyensys Knowledge Portal




Monday, July 16, 2018

OPP "outofmemory" best practices

The "outofmemory" error occurs
- when the Output Post Processor does not have sufficient heap size per process defined to handle the large report
- when processing large reports during peak utilization times and the environment is not tuned
- when there are coding errors in the data template

Please find the best practices of OPP process as suggested by Oracle Support as follows,

a. Templates generated using BI Publisher (11g or 12c) are not supported by the EBS. Please use the BI Publisher Desktop version meant for the EBS application and recreate your template using it.

Details to get BIP for EBS:
The BI Publisher Desktop version meant for the EBS application (xdo 5.6.3) is obtained from patch 12395372.
When installed it will show as version 10.1.3.2.1 in MS Word.

Reference:
Section 3. Latest XML Publisher Desktop Patch from:
Note 1138602.1 - Overview of Available Patches for Oracle XML Publisher embedded in the Oracle E-Business Suite

10.1.3.2.1 is certified only with MS Office 2003 and 2007.


b. The scalability setting SHOULD NOT be set at the site level. Set the scalability settings to False at the Site level. Only set scalability settings to True at the template level of large reports.
1. Sign on as the XML Publisher Administrator
2. Navigate to Administration Page
3. Click on the 'FO Processing' plus sign and set the following to 'False' or leave blank:
4. Use XML Publisher's XSLT processor
5. Enable scalable feature of XSLT processor
6. Enable XSLT runtime optimization
7. Save and bounce the managers

c. Set the scalability settings to True at the template level of large reports (including for the template of this particular report - Template code: XXAARPTOBJ)
In the XML Publisher Administration responsibility:
1. query up the Template for the concurrent program that produces a large data file:
2. click on the Edit Configurations button
3. Under the Configuration subtab:
4. Click on the 'FO Processing' plus sign and set:
Use XML Publisher's XSLT processor - True
Enable scalable feature of XSLT processor - True
Enable XSLT runtime optimization set to True
Save and bounce the managers


d. Increase the maximum Java heap size for the OPP.

1. Determine what the heap size per OPP process is currently,

select DEVELOPER_PARAMETERS from FND_CP_SERVICES
where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME = ‘FNDCPOPP’);

-The default should be:
J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m

2. Increase the Heap Space
   
update FND_CP_SERVICES
set DEVELOPER_PARAMETERS =
'J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx1024m'
where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');

OR

1. Log into applications with the System Administrator responsibility.
2. Navigate to Concurrent -> Program -> Define
3. Query the XML Publisher Template Re-Generator program
4. Set the following value for the Executable Options : -Xmx1024m
5. Save changes.
6. Retest the program.
The OPP queue can be Recreated the using $FND_TOP/patch/115/sql/afopp002.sql file as ‘APPLSYS’ user. On running the script you will be prompted for username and password.

e. Check timeout settings.
There are two new profiles options that can be used to control the timeouts:
Profile Option : Concurrent:OPP Response Timeout Internal Name : CONC_PP_RESPONSE_TIMEOUT Description : Specifies the amount of time a manager waits for OPP to respond to its request for post processing.
Profile Option : Concurrent:OPP Process Timeout Internal Name : CONC_PP_PROCESS_TIMEOUT Description : Specifies the amount of time the manager waits for the OPP to actually process the request.

No comments: