This action might not be possible to undo. Are you sure you want to continue?
1] Modified 24-JUN-2011 In this Document Purpose Last Review Date Instructions for the Reader Troubleshooting Details Type TROUBLESHOOTING Status PUBLISHED
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
createTextNode(XMLDocument.java:3000) at oracle.reflect. Troubleshooting Details Generic errors can be resolved by performing the following steps: Insure the latest XDK patchset has been applied to the environment.apps.java:997) at oracle.apps.parser.XMLDocument.invokeParse(XSLT10gR1. Please download and review the readme and pre-requisites for Patch 7687414 .FOUtility.processTemplate(TemplateHelper.java:3459) at oracle.parser. When possible.xdo. 3. 2.xdo.Method.DelegatingMethodAccessorImpl.oa.java:3548) at oracle.XSLT10gR1.template.fo.java:343) at oracle. diagnostic tools are included in the document to assist in troubleshooting.parse(XMLParser.invoke(DelegatingMethodAccessorImpl.effortreporting.xdo. For 12i Environments: 1.generateFO(FOUtility.java:285) at oracle.XSLTWrapper.parser.java:975) at oracle.apps.XMLDocument. 7339075.xml.transform(XSLT10gR1.xdo.java:338) at oracle.at oracle.fnd.invoke(Method.server. Please download and review the readme and pre-requisites for Patch 7697388 .psp.xdo.xdo.template.transform(XSLTWrapper.TemplateHelper.parser.NonValidatingParser.runProgram(EffortReportCP.xml. 2.common.xdo.reflect.apps.v2.xdo.apps.parser.java:1044) at oracle.server. Please retest the issue.main(Run.xdo.EffortReportCP.cp.java:39) at sun.TemplateHelper. .xdo.REHOSTING XDOPARSER 10.TemplateHelper.FOUtility.xdo.xdo.apps.v2.apps.v2.fo.characters(DocumentBuilder.xdo.NativeMethodAccessorImpl.v2.REHOSTING XDOPARSER 10.xdo. Please apply Patch 7687414 in a test environment.apps.java:553) at oracle.parseDocument(NonValidatingParser.fo.parser. For 11i Environments: 1.NonValidatingParser.java:1391) at oracle.Run.XMLParser. Please retest the issue.java:157) Last Review Date November 20.createNodeFromType(XMLDocument.parser.NonValidatingParser.schema.parser.invoke(NativeMethodAccessorImpl.apps.oa.xdo.v2. 7339075 FOR 11I.0.template.processTemplate(TemplateHelper.oa.java:735) at oracle.java:212) at oracle.parser.java:2869) at oracle.invoke0(Native Method) at sun.java:517) at oracle.parseText(NonValidatingParser.schema.1.createFO(FOProcessor.request.createNodeFromType(XMLDocument.NativeMethodAccessorImpl.reportCharacters(NonValidatingParser.lang.util.util.v2.generateFO(FOUtility.runProcessTemplate(TemplateHelper.java:1680) at oracle.v2. please migrate the solution as appropriate to other environments.DocumentBuilder.xdo.apps.v2.v2.xdo.NonValidatingParser.common.1.reflect.generate(FOProcessor.template.parseElement(NonValidatingParser. 2010 Instructions for the Reader A Troubleshooting Guide is provided to assist in debugging a specific issue.5 WITH FIX FOR BUG 7586025. If the issue is resolved.common.v2.0. 3.FOProcessor.5 WITH FIX FOR BUG 7586025.java:177) at oracle.parseRootElement(NonValidatingParser.server. Please apply Patch 7697388 in a test environment.generateFO(FOUtility.FOProcessor.java:224) at oracle.xdo.NonValidatingParser.parser.util.template.xdo.xdo.apps.xml.java:289) at sun.FOUtility.java:25) at java. 4.schema.XSLT10gR1.apps.java:597) at oracle.xdo.java:1665) at oracle.java:5936) at oracle.XMLDocument.reflect.apps.java:1268) at oracle.
1 . OR Configure the XML Publisher Administrator Configuration settings.4.GSMServiceController:-mx1024m' where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME = 'FNDCPOPP'). 2. The default should be: J:oracle. Under FO Processing. Retest the program. 6.4.gsf. Increase the Heap Space per Process to 1024: update FND_CP_SERVICES set DEVELOPER_PARAMETERS = 'J:oracle.apps. OR 1. 1.cp.gsf.fnd. OR 1. 4.fnd. 6. Save changes.6. If the issue is resolved. 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. At a minimum the installed version should be 1.CMCLEAN. Currently the latest version is 1. 5.GSMServiceController:-mx512m 3. Run cmclean. 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. Bring the managers up again. 2. In addition.apps. This should be at least 5GB or 20x larger than largest XML data file you generate 3. Reports built with large images will require additional space.cp. Overview of Bug/Patch References: Oracle E-Business Suite 12i: Bug 7504336 ONDEMAND:XML Error in the Create Accounting . Bring the managers down. Set the following value for the Executable Options : -Xmx1024m 5. please migrate the solution as appropriate to other environments. Query the XML Publisher Template Re-Generator program 4. 2.sql script from Note 134007. Navigate to Concurrent -> Program -> Define 3. the latest XDO patchset should be applied in the environment to insure the latest XML Publisher codeset is being utilized. So please insure there is adequate temp space and your code is optimized when running large reports/templates. Log into applications with the System Administrator responsibility. As XML Publisher Administrator navigate to Administration->Configuration. Under Temporary Directory pick a temporary file location on your concurrent processing node.
lang. you should look inside our BI Publisher community under Discussions. setup.OUTOFMEMORYERROR: JAVA HEAP SPACE FOR ARXAPPJR Bug 9532372 JE Report Gives Error "JAVA. o Please search on only the relevant information.Failed With JAVA HEAP Space Error. Do you have a question about BI Publisher (install. o This community offers 24-hour turn-around responses (Monday to Friday) to your most pressing questions and concerns. and do not include pronouns.1 How to Configure the Account Analysis Report in Release 12 for Large Reports Note 747750.Lang. conjunctions or prepositions unless it is part of the error message that is generated.1 Report Manager FRM_TO_GENERATOR module:FO Generator .OutOfMemoryError Note 737311.lang.LANG.1 XML Publisher Data Template Request XDODTEXE Fails with Java.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].Bug 7680519 OPP Error in CST JELINES Report Due to java. Exception in thread "main" java.1 R12 Format Payment Instruction Failed With the Error Java Exception in Thread "Main" java.OUTOFMEMORYERROR:JAVA HEAP SPACE Note References: Note 390968.LANG. use KEYWORDS and ERRORS.LANG. .1 Investigating BI Publisher Errors such as Acct Analysis Report Ends in Java Heap Error Note 987670.JAVA HEAP SPACE While Executing XML Report Bug 9890082 REPORT FAILING WITH JAVA.1 Out of Memory Error When Running XML Publisher Template Re-Generator Concurrent Program Note 876227. patch or certification? If YES. usage.OUTOFMEMORYERROR:JAVA HEAP SPACE Bug 9441214 JAVA.lang.outofmemoryerror: java heap space Bug 8973110 CSTACRAP JAVA.LANG.LANG. Tips and Tricks.1 XML Error in Subledger Period Close Report Note 788935. White Papers or start a new Discussion yourself.OutOfMemoryError: Java heap space Note 751835.OUTOFMEMORYERROR. bug. etc.OUTOFMEMORYERROR:JAVA HEAP SPACE" Bug 9677198 Getting JAVA.OutOfMemoryError: Java heap space Note 1082672. It also lists our previously recorded and planned future Webcasts.) or need a clarification about a BI Publisher note.
JAVA.LANG. OPP.OUTOFMEMORYERROR. HEAP ERRORS. PUBLISHER. OUTPUT POST PROCESSOR.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. XML PUBLISHER Errors JAVA HEAP SPACE Back to top . XDODTEXE.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.