Categories
- All Categories
- 75 Oracle Analytics News
- 7 Oracle Analytics Videos
- 14K Oracle Analytics Forums
- 5.2K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 40 Oracle Analytics Trainings
- 59 Oracle Analytics Data Visualizations
- 2 Oracle Analytics Data Visualizations Challenge
- 3 Oracle Analytics Career
- 4 Oracle Analytics Industry
- Find Partners
- For Partners
OAC Workaround to bypass the data preparation limits on OCPU basis
Summary
data preparation Limits
Content
While data preparation customers hitting the limit 125,000 with 1OCPU which is expected.
Customer asking, what if when a query returns more than 2,200,000 rows to process, which is high watermark @16 OCPU. How to handle the rows on data preparation more than the OCPU limit? Do we have any workarounds?
Data Preparation limits
Version
106.x
Bala Guddeti |
Principal Analytics Technologist
https://www.linkedin.com/in/balaguddeti-oracledataintelligence/
Answers
-
Look at the query limits. I believe having just 2 OCPU should suffice your needs. If there are analysis requiring to process higher number of rows. Please create a aggregate table to store data and navigate RPD LTS to retrieve data at higher grain using aggregate tables. If data is required at lower granularity level then obviously it will be required with set of additional filter conditions. This way, you can control user needs efficiently.
Hope this helps.
Which compute size do you think you’ll need? Limits when querying data for visualizations, analyses, and dashboards Max input rows returned from any data source query 1 OCPU
(trials only)
125,000
2 OCPU
1,100,000
0
