Categories
- All Categories
- 4 Oracle Analytics Sharing Center
- 9 Oracle Analytics Lounge
- 187 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.4K Oracle Analytics Forums
- 5.9K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 63 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
What is the limitation on number of rows we can download using OTBI report

Hi,
we have created a OTBI report for Item master but when we download using csv it can download only 75000 rows. so want to know if there is any limitation on number of rows that can be downloaded using OTBI report.
Rgds,
pradeep
Best Answer
-
Hello @User_W7SY0
I understand your point. We try to compliment the documentation with KM Articles. For example:
FAW:FDI:FDIP Export To Excel Is Exporting Only 25000 Rows For Visualizations (Doc ID 3027775.1)
@Pradeep kudale FYI, there is an OTBI community here:
Regards,
John
0
Answers
-
Hi Pradeep,
FAW does not have a limitation. The limitation likely comes from OAC or BI Publisher if you are using that. You should check OAC documentation for limitations based on the number of OCPUs. https://docs.oracle.com/en/cloud/paas/analytics-cloud/acoci/create-services.html#GUID-7D6DB4EE-8DD5-44C5-9B6E-9FA847463A5F
0 -
Workbooks (the new analysis format in FAW/FDI) currently only allows for 25,000 rows to be exported to Excel. CSV export can go up to 4,000,000 I believe.
I think Oracle needs to be extremely clear about this and not ask users/customers to navigate a million different documents to get an answer for these types of questions. It's very clear what users/customers expect with respect to export data from reports.
7 -
In Oracle Transactional Business Intelligence (OTBI), the limitation for downloading reports is typically set at 75,000 rows when exporting to CSV format. This limit is imposed to optimize performance and manageability, especially for larger datasets.
If you need to work with larger datasets, consider the following options:
- Use Filters: Narrow down your report criteria to reduce the number of rows.
- Scheduled Reports: Instead of downloading directly, schedule the report to be sent via email, which may allow larger datasets to be processed.
- Use BI Publisher: If you require more flexibility in the number of rows exported, consider using Oracle BI Publisher, which can handle larger datasets more effectively.
For further details and insights, you can check the official Oracle documentation or forums discussing OTBI limitations and best practices.
Thanks and regards,
Jayant Deshmukh
1 -
I'd like to point out that we keep hearing about "performance and manageability" when raising concerns about export limitations in the era of Big Data. These export restrictions are understandable in the past when bandwidth, storage and compute were limited. This is simply no longer the case in the modern era.
I'm still of the opinion export restrictions should be set higher and/or up against the limitation of a specific format (such as modern excel supporting up to a million rows).
3