Hi Team,
We would like to proceed with submitting an Enhancement Request (ER) to Oracle Product Management to increase the supported Maximum Query Limit from 660 seconds (11 minutes) to 1,200 seconds (20 minutes) in Oracle Analytics Cloud.
Please find the requested information below.
Business Justification
We recently migrated our enterprise reporting platform from Oracle Business Intelligence Enterprise Edition (OBIEE 12c) to Oracle Analytics Cloud (OAC) without changing the existing reporting architecture, business logic, or scheduling framework.
Several business-critical reports and scheduled agents supporting Finance, Manufacturing, and Supply Chain occasionally require 10–15 minutes to complete due to the volume and complexity of Oracle EBS data. These same reports and agents have executed successfully in our OBIEE Production environment for several years. The current maximum supported query timeout of 11 minutes in OAC prevents these business processes from completing successfully.
Business Impact
This limitation directly impacts our Financial Month-End Close activities.
Our investigation confirmed that:
- Dashboards execute successfully when run manually from the OAC UI.
- Child agents complete successfully when execution remains below approximately 10 minutes.
- Executions consistently fail whenever runtime exceeds approximately 11 minutes.
- Oracle Support confirmed this behavior aligns with the configured Maximum Query Limit of 660 seconds.
As a result:
- Critical month-end reporting jobs fail.
- Automated report distribution to Finance users is interrupted.
- Manual execution and monitoring are required, delaying financial close activities.
- Processes that operated successfully in OBIEE cannot be executed reliably after migration to OAC.
Use Case
The request applies to enterprise scheduled reporting workloads, including:
- Financial Month-End Close reporting
- Consolidated Financial reporting
- Oracle Analytics Agents with chained child agents
- Large scheduled dashboards and reports processing Oracle EBS transactional data
These workloads are business-critical and support multiple Finance stakeholders.
Frequency
The issue occurs regularly during scheduled executions, particularly during Financial Month-End Close. While reports generally complete within 10 minutes, execution occasionally increases to 11–15 minutes because of normal transaction volume and database workload, causing the executions to fail due to the current timeout limit.
Workarounds
During this SR, we evaluated SQL optimization, analysis optimization, running child agents individually, dashboard review, database performance validation, and manual dashboard execution.
Manual execution succeeds but is not a practical workaround for scheduled production processes. These reports have already been tuned over several years, the business requires complete datasets for financial reporting, and splitting reports or reducing data volume would impact established business processes. Since the same reports executed successfully in OBIEE prior to migration, the limitation is due to the current supported timeout in OAC rather than report design.
For these reasons, we request Oracle Product Management to consider increasing the supported configurable query timeout to 20 minutes for customers with legitimate enterprise reporting workloads.
Thanks
Sayak
