Oracle Analytics Cloud and Server

Products Banner

OAC Workaround to bypass the data preparation limits on OCPU basis

Received Response
104
Views
1
Comments

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

https://docs.oracle.com/en/cloud/paas/analytics-cloud/acsom/create-services-oracle-analytics-cloud.html#GUID-164D8568-9AE3-4A74-9F1A-0D87B78713C9

Version

106.x

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

    space

    2 OCPU

    1,100,000