Sizing Business Intelligence Publisher Components To Handle Large Volumes of Data with E-Business Suite XML Publisher / BI Publisher
(Doc ID 1630732.1)
Last updated on JUNE 07, 2021
Applies to:BI Publisher (formerly XML Publisher) - Version 10.1.3.2.0 to 18.104.22.168.x [Release 10.1 to 11.1]
Oracle Concurrent Processing - Version 12.2.4 to 12.2.4 [Release 12.2]
Information in this document applies to any platform.
Provide a consolidated reference for all sizing issues with various technology components of Oracle E-Business Suite and BI Publisher.
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
|Oracle database sizing recommendations for BI Publisher|
|Recommendations to handle large volumes of data|
|1. Insure the latest ATG RUP and XDO patchsets has been applied in your environment for better report processing performance.|
|2. Set the heap size value to handle large reports while using Oracle BI Publisher.|
|3. Increase the number of Output Post Processor (OPP) to avoid/overcome the "Out of Memory Exception" error.|
|4. Enable the scalable feature|
|5. Select a temporary file location on your concurrent processing node to avoid/overcome the "Out of Memory Exception" error.|
|6. Configure the Output Post Processor's JVM.|
|7. Configure XML Reports with Large Data Sets using sort function to avoid java.lang.StackOverflowError (See <Note 1100253.1>)|
|Recommendations on Output Post Processer (OPP) Tuning|
|1. Prevent timeout errors by setting recommended OPP related profile option values|
|2. Improve performance by tuning the Output Post Processor (OPP)|
|Recommendations on Client Side Tools - Excel limits|
|1. Be sure to understand Microsoft Excel specifications and limits (See <Note 1469264.1>)|
|2. Increase the default amount of 80 characters stored per row to increase the data size to around 20MB (See <Note 889482.1>)|
|3. Use Excel binary output files to avoid the large verbose XHTML format output. |