Output Post Processor java heap size issue for larg output reports. RESOLVED

-

Hi,

During running long report in EBS R12.2 usually give below error and here the solution, I used multiple times and it works.

Error:
java.lang.OutOfMemoryError: Java heap space
at oracle.jdbc.driver.T4CCallableStatement.allocateTmpByteArray(T4CCallableStatement.java:259)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:204)
at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:1111)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1488)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3769)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3954)
at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:9353)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1539)
at oracle.apps.fnd.cp.opp.OPPAQMonitor.waitForMessage(OPPAQMonitor.java:435)
at oracle.apps.fnd.cp.opp.OPPAQMonitor.run(OPPAQMonitor.java:120)
at java.lang.Thread.run(Thread.java:724)
[1/16/17 6:36:14 AM] [53353:RT1529751] Output file was found but is zero sized - Deleted
[1/16/17 6:36:14 AM] [UNEXPECTED] [53353:RT1529751] java.lang.reflect.InvocationTargetException 




The 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,
- when there are coding errors in the data template
- or when memory leaks requiring patching for more current code.

You can use these steps to prevent JAVA memory errors:


1. in XML Publisher Administrator responsibility navigate to Administration > Configuration

- under : Properties -> General -> set a temporary directory

This directory should be at least 5 times larger than the largest anticipated data file.

Support recommends the directory to be at least 5GB.



2. in XML Publisher Administrator responsibility navigate to Data Definition

Although the scalable feature of the XSLT can be set at the Site level, it is recommended to enable it rather at the Data Definition level for those concurrent programs that are expected to produce large XML data files.

Navigation Path : XML Publisher Administrator responsibility

- query the data definition used by the report with large data

- on the View Data Definition page select Edit Configuration button

- set 'Use XML Publisher's XSLT processor' to True

- set 'Enable scalable feature of XSLT processor' to True

- set 'Enable XSLT runtime optimization' to True

Note that these property values, when set at the Data Definition level, takes precedence over values set at the Site level.



3. Then, in System Administrator resp, navigate to Profile > System

- set Concurrent:OPP Process Timeout = 43200

- set Concurrent:OPP Response Timeout = 43200

(these values are for 12 hours in seconds)


4. Restart the Concurrent Managers.

5a. Determine the heap size per OPP process:

select DEVELOPER_PARAMETERS from FND_CP_SERVICES

where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES

where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');

(the default is: J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m)



5b. You can increase the heap space per process, in multiples of 512,

to the LIMITATION of the JAVA capabilities on the concurrent SERVER. The FNDOPP concurrent manager runs 32-bit java which can be maximized to 2GB (2048), for 64 bit systems the maximum recommendation is 3072:

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

6. Restart the Concurrent Managers.


For a documented reference, please see the following notes:

note:1399454.1 - Tuning Output Post Processor (OPP) to Improve Performance
note:1982181.1 - How to Resolve Output Post Processor Giving Errors On Large Reports?
Investigating BI Publisher Errors such as Acct Analysis Report Ends In Java Heap Error ( Doc ID 876227.1 )
Sizing BIP Components To Handle Large Volumes of Data with E-Business Suite XML Publisher / BI Publisher ( Doc ID 1630732.1 )

Comments

Post a Comment

Popular posts from this blog

RMAN backup Status (Remaining Time and Percentage)

-
On Running a huge database backup we often need to know the status of backup. 1) How much backup is taken. 2) How much is remain. 3) Estimate time to complete the backup. After lot of search i find out this amazing query below. col dbsize_mbytes for 99,999,990.00 justify right head "DBSIZE_MB" col input_mbytes for 99,999,990.00 justify right head "READ_MB" col output_mbytes for 99,999,990.00 justify right head "WRITTEN_MB" col output_device_type for a10 justify left head "DEVICE" col complete for 990.00 justify right head "COMPLETE %" col compression for 990.00 justify right head "COMPRESS|% ORIG" col est_complete for a20 head "ESTIMATED COMPLETION" col recid for 9999999 head "ID" select recid , output_device_type , dbsize_mbytes , input_bytes/1024/1024 input_mbytes , output_bytes/1024/1
Read more

EBS R12.2 Autoconfig Failed. Resolved

-
Hi, Please do the following and retest the issue: Due to the method required for "cleaning out" / "re-synchronizing" the following tables, it is EXPECTED / REQUIRED that the Applications have been shutdown. The only thing running should be the Database Tier. Note: A full backup should also be taken before any testing begins. Test the following steps in a development instance, and then migrate accordingly once the desired result is confirmed: 1. Backup the fnd_oam_context_files, fnd_nodes, and adop_valid_nodes tables in the EBS env: sqlplus applsys/pwd create table fnd_oam_context_files_bkp as select * from fnd_oam_context_files; create table fnd_nodes_bk as select * from fnd_nodes; create table adop_valid_nodes_bk as select * from adop_valid_nodes; 2. Truncate the following tables: truncate table fnd_oam_context_files; truncate table fnd_nodes; truncate table adop_valid_nodes; 3. Run AutoConfig on the DB tier
Read more

Cleaning nodes in EBS databae.

-
Cleaning EBS nodes with EXEC FND_CONC_CLONE.SETUP_CLEAN; . EBSapps.env run   $ sqlplus apps/<PASSWORD> SQL> create table fnd_nodes_22ep14 as select * from fnd_nodes; SQL> exec fnd_conc_clone.setup_clean; PL/SQL procedure successfully completed. SQL> commit; Commit complete. After that run autoconfig in below order to populate the FND TABLES properly. 1) Stop application services ( optional but  recommended )  2) Run autoconfig on dbTier 3) Run autoconfig on appTier
Read more