Large Reports are Not Produced When Using BI Publisher Scheduler
(Doc ID 1088838.1)
Last updated on DECEMBER 23, 2023
Applies to:
BI Publisher (formerly XML Publisher) - Version 10.1.3.4.0 to 10.1.3.4.1 [Release 10.1]Information in this document applies to any platform.
Symptoms
BI Publisher reports using the scheduler appear to run continuously with no output generated.
Log shows a Java memory error:
[040910_105048583][][EXCEPTION] java.lang.OutOfMemoryError: Java heap space
at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:99)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:393)
at java.lang.StringBuffer.append(StringBuffer.java:225)
at oracle.apps.xdo.service.report.saw.SawRowSetDataHandler.endElement(SawRowSetDataHandler.java:119)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1318)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:336)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
etc etc etc
at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:99)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:393)
at java.lang.StringBuffer.append(StringBuffer.java:225)
at oracle.apps.xdo.service.report.saw.SawRowSetDataHandler.endElement(SawRowSetDataHandler.java:119)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1318)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:336)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
etc etc etc
Cause
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
| Symptoms |
| Cause |
| Solution |