You are on page 1of 5

Output Post Processor (OPP) Log Contains Error "java.lang.OutOfMemoryError: Java heap space" [ID 1268217.

1] Modified 24-JUN-2011 In this Document Purpose Last Review Date Instructions for the Reader Troubleshooting Details Type TROUBLESHOOTING Status PUBLISHED

Applies to:
BI Publisher (formerly XML Publisher) - Version: 12.0 to 12.0 - Release: 12.0 to 12.0 BI Publisher (formerly XML Publisher) - Version: 5.6.3 to 5.6.3 [Release: 5 to 5] BI Publisher (formerly XML Publisher) - Version: 11.5 to 11.5 [Release: 11.5 to 11.5] Information in this document applies to any platform.

This document is intended for System Administrators. This note is generic in nature and is not designed to address product-specific issues. Individual product data is to be addressed by the product team that owns the XML data. The purpose of this document is to outline bugs/patches, notes, knowledge base, and community resources for addressing the error "java.lang.OutOfMemoryError: Java heap space". The error occurs when there is limited heap space in the JVM to process the report, the Java application running is out of memory, the scalable feature isn't enabled, an older version of the JRE is being used in the configuration, there is insufficient space in the designated temp directory for processing the report, and reports are embedded with images which require a lot of space that unavailable. Enabling the scalable feature controls the scalable feature of the XDO parser. If you know you are going to return a large dataset or have a long running query you can specify that the data engine enter scalable mode. By turning on the scalable option this will cause the data engine to use the disk rather than use memory to generate the output. When this error occurs in one report, subsequent reports will likely not have any output and will end up with errors also.

To obtain the Output Post Processor log file, follow the navigation below: 1. Select the System Administrator responsibility. 2. Select the menu Concurrent - Manager - Administer. 3. Select the Output Post Processor Service. 4. Select the Processes button. 5. Select Manager Log. 6. The log will contain a java stack error similar to the following: java.lang.reflect.InvocationTargetException Caused by: java.lang.OutOfMemoryError: Java heap space

XSLT10gR1.xdo.template.5 WITH FIX FOR BUG 7586025.apps.parseRootElement(NonValidatingParser.apps.template.XMLParser.processTemplate( at at at sun.xdo. at oracle.createNodeFromType(XMLDocument. Please download and review the readme and pre-requisites for Patch 7697388 .DocumentBuilder.invoke(DelegatingMethodAccessorImpl.apps.Run.TemplateHelper.oa.XMLDocument.characters( at oracle.xdo.5 WITH FIX FOR BUG at at oracle.template. When possible.XSLTWrapper.transform(XSLTWrapper. at oracle.oa.reflect.generateFO(FOUtility.REHOSTING XDOPARSER at at at oracle.xdo.xdo. 3.util.xdo.parser.server.fnd.common.invoke(NativeMethodAccessorImpl.xdo. For 11i Environments: 1.server.reportCharacters( oracle.v2.transform(XSLT10gR1.parser.parseText(NonValidatingParser.1.main(Run.effortreporting.server.reflect.invoke0(Native Method) at at at oracle.NonValidatingParser. diagnostic tools are included in the document to assist in troubleshooting.TemplateHelper.psp.apps.0.createTextNode(XMLDocument.1.apps.NonValidatingParser.runProgram(EffortReportCP.NonValidatingParser.parser.generateFO( at oracle.parseDocument(NonValidatingParser.v2. Troubleshooting Details Generic errors can be resolved by performing the following steps: Insure the latest XDK patchset has been applied to the environment. If the issue is resolved.xdo.createNodeFromType(XMLDocument. Please apply Patch 7697388 in a test environment.apps.xdo.schema.invoke(Method.oa. 2. 7339075.xdo.apps. 7339075 FOR 11I.parser.parser.createFO( Last Review Date November at at oracle. at at at oracle.DelegatingMethodAccessorImpl.REHOSTING XDOPARSER 10.xdo. Please retest the issue.xdo.xdo. Please apply Patch 7687414 in a test environment. Please download and review the readme and pre-requisites for Patch 7687414 .apps.xml.generate(FOProcessor.parse( at at oracle.xml. Please retest the at oracle.XMLDocument.parser.lang.v2. please migrate the solution as appropriate to other at oracle.schema.0.parser.apps.parser.parseElement(NonValidatingParser.v2.reflect.runProcessTemplate(TemplateHelper.xdo.EffortReportCP. For 12i Environments: at at oracle.NonValidatingParser. 2010 Instructions for the Reader A Troubleshooting Guide is provided to assist in debugging a specific issue. 4.v2.common.generateFO(FOUtility.v2.processTemplate(TemplateHelper.FOProcessor.

fnd. Currently the latest version is 1.gsf. OR 1. 2. Bring the managers up again.gsf.GSMServiceController:-mx1024m' where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME = 'FNDCPOPP'). Set the following value for the Executable Options : -Xmx1024m 5. Under FO Processing. OR 1.cp. Navigate to Concurrent -> Program -> Define 3. 6. the latest XDO patchset should be applied in the environment to insure the latest XML Publisher codeset is being utilized. 2.sql script from Note 134007. If the issue is resolved. So please insure there is adequate temp space and your code is optimized when running large reports/templates.apps.4. Save changes. OR Configure the XML Publisher Administrator Configuration settings. In addition.1 .6.apps.CMCLEAN. 2.GSMServiceController:-mx512m 3. Query the XML Publisher Template Re-Generator program 4. Bring the managers down.cp. At a minimum the installed version should be 1. please migrate the solution as appropriate to other environments. 6. Log into applications with the System Administrator responsibility. Under Temporary Directory pick a temporary file location on your concurrent processing node. Run cmclean. 1. Overview of Bug/Patch References: Oracle E-Business Suite 12i: Bug 7504336 ONDEMAND:XML Error in the Create Accounting . 4. This should be at least 5GB or 20x larger than largest XML data file you generate 3. 5.fnd. As XML Publisher Administrator navigate to Administration->Configuration. Reports built with large images will require additional space. set: o Use XML Publisher's XSLT processor set to True o Enable scalable feature of XSLT processor set to False o Enable XSLT runtime optimization set to True Note: Upgrading to a newer version of the JRE is also a good idea. Retest the program. Increase the Heap Space per Process to 1024: update FND_CP_SERVICES set DEVELOPER_PARAMETERS = 'J:oracle.4. The default should be: J:oracle. 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').SQL Non-Destructive Script to Clean Concurrent Manager Tables.

OUTOFMEMORYERROR: JAVA HEAP SPACE FOR ARXAPPJR Bug 9532372 JE Report Gives Error "JAVA.lang. patch or certification? If YES. Tips and Tricks.LANG.1 How to Configure the Account Analysis Report in Release 12 for Large Reports Note 747750.lang.1 Out of Memory Error When Running XML Publisher Template Re-Generator Concurrent Program Note 876227.OutOfMemoryError: Java heap space Note 751835.  Do you have a question about BI Publisher (install.Failed With JAVA HEAP Space Error. and do not include pronouns.OutOfMemoryError Note 737311.lang. use KEYWORDS and ERRORS.JAVA HEAP SPACE While Executing XML Report Bug 9890082 REPORT FAILING WITH JAVA. setup. Exception in thread "main" java. o This community offers 24-hour turn-around responses (Monday to Friday) to your most pressing questions and concerns.OutOfMemoryError: Java heap space Note 1082672.LANG. etc.OUTOFMEMORYERROR:JAVA HEAP SPACE" Bug 9677198 Getting JAVA.1 R12 Format Payment Instruction Failed With the Error Java Exception in Thread "Main" java.LANG.1 Report Manager FRM_TO_GENERATOR module:FO Generator .1 How to Configure the Account Analysis Report in Release 12 for Large Reports ADDITIONAL RESOURCES FOR BI Publisher/XML Publisher  SEARCH our BI Publisher knowledge area for a response to your issue [Navigation in My Oracle Support: “Knowledge” Tab then type “BI Publisher (formerly XML Publisher)” in “Select Product” then click to go to knowledge].OUTOFMEMORYERROR:JAVA HEAP SPACE Bug 9441214 JAVA. conjunctions or prepositions unless it is part of the error message that is generated.OUTOFMEMORYERROR:JAVA HEAP SPACE Note References: Note 390968. usage.Bug 7680519 OPP Error in CST JELINES Report Due to java.1 XML Error in Subledger Period Close Report Note 788935. o Please search on only the relevant information.LANG. White Papers or start a new Discussion yourself.OUTOFMEMORYERROR.1 XML Publisher Data Template Request XDODTEXE Fails with Java. . bug.1 Investigating BI Publisher Errors such as Acct Analysis Report Ends in Java Heap Error Note 987670. It also lists our previously recorded and planned future Webcasts.outofmemoryerror: java heap space Bug 8973110 CSTACRAP JAVA.Lang.LANG.) or need a clarification about a BI Publisher note. you should look inside our BI Publisher community under Discussions.

XML PUBLISHER Errors JAVA HEAP SPACE Back to top . PUBLISHER.LANG. OUTPUT POST PROCESSOR. HEAP ERRORS.OUTOFMEMORYERROR.Related Products    Oracle E-Business Suite > Applications Technology > Technology Components > BI Publisher (formerly XML Publisher) Oracle E-Business Suite > Applications Technology > Technology Components > BI Publisher (formerly XML Publisher) Oracle E-Business Suite > Applications Technology > Technology Components > BI Publisher (formerly XML Publisher) Keywords HEAP. OPP. JAVA. XDODTEXE.