Here you go

Showing posts with label OPP Error. Show all posts
Showing posts with label OPP Error. Show all posts

Friday, August 26, 2016

Find OPP Error and Resolve XML Report Warnning


How to Resolved Error Caused by: java.lang.OutOfMemoryError: Java heap space


SELECT fcpp.concurrent_request_id req_id, fcp.node_name, fcp.logfile_name
  FROM fnd_conc_pp_actions fcpp, fnd_concurrent_processes fcp
 WHERE fcpp.processor_id = fcp.concurrent_process_id
   AND fcpp.action_type = 6
   AND fcpp.concurrent_request_id = &request_id;







To investigate on XML issues or other publishing problems, often the OPP logfile is needed.
OPP stands for Output Post Processor. Below are the steps to find log file

1. Login to the application as SYSADMIN

2. Responsibility: System Administrator

3. Function: Concurrent --> Manager --> Administration

4. Select the Output Post Processor

5. Click on the Processes button

6. Select the Concurrent Process which was active during the time that the request ran

7. Click on the Manager Log button to open the Output Post Processor log file






/*

[5/18/16 6:55:24 PM] [252991:RT4384126] Output file was found but is zero sized - Deleted

[5/18/16 6:55:24 PM] [UNEXPECTED] [252991:RT4384126] java.lang.reflect.InvocationTargetException

    at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at oracle.apps.xdo.common.xml.XSLT10gR1.invokeParse(Unknown Source)
    at oracle.apps.xdo.common.xml.XSLT10gR1.transform(Unknown Source)
    at oracle.apps.xdo.common.xml.XSLTWrapper.transform(Unknown Source)
    at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
    at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
    at oracle.apps.xdo.template.FOProcessor.createFO(Unknown Source)
    at oracle.apps.xdo.template.FOProcessor.generate(Unknown Source)
    at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5984)
    at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3475)
    at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3564)
    at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:311)
    at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:185)

Caused by: java.lang.OutOfMemoryError: Java heap space

    at oracle.xdo.parser.v2.XMLDocument.xdkIncCurrentId(XMLDocument.java:3020)
    at oracle.xdo.parser.v2.XMLNode.xdkInit(XMLNode.java:2758)
    at oracle.xdo.parser.v2.XMLNode.(XMLNode.java:423)
    at oracle.xdo.parser.v2.CharData.(CharData.java:118)
    at oracle.xdo.parser.v2.XMLText.(XMLText.java:168)
    at oracle.xdo.parser.v2.XMLDocument.createNodeFromType(XMLDocument.java:2869)
    at oracle.xdo.parser.v2.XMLDocument.createNodeFromType(XMLDocument.java:3000)
    at oracle.xdo.parser.v2.XMLDocument.createTextNode(XMLDocument.java:735)
    at oracle.xdo.parser.v2.DocumentBuilder.characters(DocumentBuilder.java:553)
    at oracle.xdo.parser.v2.NonValidatingParser.reportCharacters(NonValidatingParser.java:1680)
    at oracle.xdo.parser.v2.NonValidatingParser.parseText(NonValidatingParser.java:1391)
    at oracle.xdo.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1268)
    at oracle.xdo.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:338)
    at oracle.xdo.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:285)
    at oracle.xdo.parser.v2.XMLParser.parse(XMLParser.java:289)

*/



select developer_parameters from  fnd_cp_services
WHERE service_id = (SELECT manager_type
FROM fnd_concurrent_queues
WHERE concurrent_queue_name = 'FNDCPOPP');

You simply increase the value.


   UPDATE fnd_cp_services SET developer_parameters =
'J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx4096m'
WHERE service_id = (SELECT manager_type
FROM fnd_concurrent_queues
WHERE concurrent_queue_name = 'FNDCPOPP');

Commit;

Bounce the application and  retest.

Friday, April 8, 2016

Output Post Post Processor Error : java.lang.OutOfMemoryError: GC overhead limit exceeded


Output Post Post Processor Error : java.lang.OutOfMemoryError: GC overhead limit exceeded



If you receive error on Report's Log:


Post-processing of request failed at 06-APR-2016 12:44:49 with the error message:
One or more post-processing actions failed. Consult the OPP service log for details.

CONC-POST-PROCESSING RESULTS

-- PUBLISH:
oracle.apps.fnd.cp.opp.PostProcessorException: oracle.apps.fnd.cp.opp.PostProcessorException: oracle.apps.xdo.XDOException
 


Then check you OPP Log by using following SQL you can find OPP Log Location:

SELECT fcpp.concurrent_request_id req_id, fcp.node_name, fcp.logfile_name
FROM fnd_conc_pp_actions fcpp, fnd_concurrent_processes fcp
WHERE fcpp.processor_id = fcp.concurrent_process_id
AND fcpp.action_type = 6
AND fcpp.concurrent_request_id = &&request_id






If you receive Error like the following while Running XML Publisher/ BI Publisher Reports from Oracle E-Business Suite in OPP Log:
  

Caused by: oracle.xdo.parser.v2.XPathException: Extension function error: Error invoking 'ms_format_number':'java.lang.OutOfMemoryError: GC overhead limit exceeded'


OR

Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
    at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1067)



Then You just need to follow the Plan as Per Oracle:



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


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


3. Increase the Heap Space per Process to 1024: ( 1024 = If you want to increase the Heap Memory to 1GB) 
 
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');
 
4. Do not forget to bounce the application services.
 
You are done now.
 
 
 
 
 

For Complete Details Review the following Documents : 

 
Output Post Processor (OPP) Log Contains Error "java.lang.OutOfMemoryError: Java heap space" (Doc ID 1268217.1)
 
BI Publisher Consolidated Reference ( Doc ID 1546377.1 )
In above document please go through section 'Output Post Processing' for your error. 
 
 
Sizing BIP components for Large Volumes of Data in E-Business Suite environment (Doc ID 1599890.1)