Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 16 Oracle Analytics Lounge
- 216 Oracle Analytics News
- 43 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 79 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Dataflow run in OAC fails with a configuration having 36CPUs, that is supposed to return about 3lakh

Summary
Dataflow run in OAC fails for a huge recordset with a highend configuration
Content
Hi,
I've created a dataflow that I am expecting to return 3lakhs of records from ADW. As this is a huge dataset, I have created an OAC instance with 36 OCPUs. As per the documentation @ https://docs.oracle.com/en/cloud/paas/analytics-cloud/acsom/create-services-oracle-analytics-cloud.html#GUID-164D8568-9AE3-4A74-9F1A-0D87B78713C9, this configuration is supposed to support retrieval of about 22lakhs of records.
However, when I run the dataflow with this huge configuration, it runs for about 10min and then fails. When I click on "View Details", it says, "The user request exceeded the maximum query governing execution time." (attached this screenshot).
How do I ensure to run my dataflow successfully? Please let me know.
Thanks in advance,
Chethana
Version
105.4.0-158
Answers
-
Error Screenshot
0 -
Hello Chethana,
By default there is a limit given for each given each Oracle ADW parameter, please refer to the below steps to modify the ADW Query run time limits:
Follow these steps to set rules from the service console:
From the Autonomous Data Warehouse details page, click Service Console.
On the Service Console click Administration.
Click Set Resource Management Rules.
Select the Run-away criteria tab to set rules for consumer groups.
Select the Consumer group: HIGH, MEDIUM, or LOW.
Set runaway criteria values:
Query run time (seconds)
Amount of IO (MB)Click Save changes.
This should resolve your issue.
Best Regards,
Aman Jain0 -
Attaching screenshot for your reference here:
0 -
Thanks Aman. I have tried the above option. In fact, for all Consumer groups, the "Run-away criteria" is 0 in our case (unlimited) and was not required to tweek this.
I updated the value for CPU/IO shares. For the Medium Consumer group, that I am using, I updated it from default to 2 to 90 and still the dataflow fails. Could this be related to number of CPUs used for our ADW? We have used 1 CPU for our ADW, with 1 TB of storage capacity. Please let me know.
Thanks,
Chethana
0