Consolidation Document For Java Heap Space Error
(Doc ID 2598803.1)
Last updated on FEBRUARY 17, 2023
Applies to:Oracle Concurrent Processing - Version 12.2.7 to 12.2.11 [Release 12.2]
BI Publisher (formerly XML Publisher) - Version 5.6.3 to 12.2 [Release 5 to 12.2]
Oracle Concurrent Processing - Version 220.127.116.11 to 12.2 [Release 11.5 to 12.2]
Information in this document applies to any platform.
BI Publisher (formerly XML Publisher) - Version 11.5 to 12.2 [Release 11.5 to 12.2]
Oracle Concurrent Processing - Version 12.2.6 to 12.2.6 [Release 12.2]
Oracle Concurrent Processing - Version 12.2.4 to 12.2.4 [Release 12.2]
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"
Causes of the "Java heap space" includes the following:
- 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
- Reports are embedded with images which require a lot of space that temporarily unavailable
The following is a High Level of areas to isolate that are further detailed in the 'Troubleshooting Section':
- Upgrading to a newer version of the JRE is recommended. In addition, the latest XDO patchset should be applied in the environment to insure the latest XML Publisher code set is being utilized.
- 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 as the space allocation causes cascading affects upon other reports. This will enable garbage collection for the JVM and could eventually result in filling up the garbage collection.
- It may be required to provide the Output Post Processor log file:
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:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|The following is a High Level of areas to isolate that are further detailed in the 'Troubleshooting Section': |