Occasional error working with or exporting Fusion datasets: “PublicReportService:generateReport for reportAbsolutePath [/Custom/Quest/QuestReportCSV.xdo] failed” (4378693)

User occasionally receives the below error working with or exporting Fusion data sets. Is there a limit on the size of the output of datasets?

Error: "PublicReportService::generateReport for reportAbsolutePath [/Custom/Quest/QuestReportCSV.xdo] failed: due to oracle.xdo.server.ServerException: oracle.xdo.memoryguard.XDODataSizeLimitException: Stopped processing the report. Report data size of 524288009 bytes exceeds the maximum limit 524288000 bytes for online reports. Schedule this report."

This error occurs during the execution phase when Oracle BI Publisher pre-processes raw data before applying filters and formatting. Even if the final report output is small (e.g., under 4MB), Oracle Fusion may temporarily exceed 500MB during internal processing, causing the query to fail before reaching the export phase.

Note: The limit is about 500 MB but the entire result is under 4MB when exported

The issue is related to Oracle Fusion's internal report processing limitations. The 500MB limit applies to online reports, but data processing may temporarily exceed this limit before compression or final output is generated. The report processing and size limitations are controlled by Oracle Fusion’s BI Publisher/XDO Data Size Limit settings. The initial assumption was that the report should only retrieve 5,000 rows (~4MB when exported). However, the actual data set contains ~9 million rows (9007876), meaning the report might be processing far more data than expected before filtering.

Even if the final export is small, Fusion’s processing steps may temporarily exceed 500MB due to memory overhead.  Why Oracle Fusion Could Exceed 500MB Before Exporting Data:

• Fusion may process a larger dataset before applying filters
• Joins, aggregations, and calculations could significantly increase memory usage
• Intermediate processing in Fusion’s reporting engine can temporarily use more memory than the final result

Workarounds:

• Schedule the report instead of running it online (to bypass the online processing limit). Verify whether the report is retrieving unnecessary data
• The dataset is much larger than expected (9M rows vs. 5K rows)
• Filtering can be done in Toad Data Studio before running queries
• Optimize the SQL query to minimize processing overhead
• Try to generate reports in CSV format to reduce memory usage
• Consider splitting large reports into multiple smaller reports
• Oracle Fusion administrators can check if the XDODataSizeLimit can be increased (if justifiable)