Oracle Analytics Cloud and Server Idea Lab

Increase SQL Query Timeout from 10 minutes to 30 minutes

Delivered
932
Views
3
Comments

Description

Please increase the DEFAULT_DB_MAX_EXEC_TIME to at least 30 minutes so that our reports can run successfully in the Cloud. Currently, DEFAULT_DB_MAX_EXEC_TIME = 10 minutes, and are reports are failing with 'execeeded time limit' error.
We also noticed that most of our reports are running longer in the cloud than they do in on-prem OBIEE.

Use Case and Business Need

We have over 200 reports that calculate measures around sales,cost,units etc and perform a year over year comparison. The reports have a direct impact on our revenue, sales margin estimates for our business.
Since the reports are erroring in OAC, this means we will have to look for alternative reporting elsewhere so our business executives can get the KPI's that they need to make informed business decisions.
Our business execs have already expressed hesitation in going live with the OAC migration until this is fixed.
If we break down the report into smaller pieces, it is taking almost an hour to run and piece the report back together, time of which our executives don't have.

 

More details

We have noticed that time series measures (such as qtd, wtd, ytd etc) are taking longer time to execute as compared to on-prem OBIEE. Which has led to time-out errors because of the 10 min threshold value.
These findings have already been demosntrated in SR#: 3-23087944661 discussion phase.

Original Idea Number: 550dc5c643

4
4 votes

Delivered · Last Updated

Comments

  • We are working on an ability to allow a certain fraction of queries to exceed the default execution time.  The initial phase of this capability is available as part of the OAC 5.6 release and will continue to be enhanced in later releases.

  • Jo-
    Jo- ✭✭

    hi Alan,
    1-Does this this feature apply to us too, we are connecting to an on-prem database from OAC via the RDG? 
    2-Could you please provide documentation around this feature (i.e. how it works, the algorithm behind it, which databases the feature is supported on)?

     

     

  • The timeout limit increased in 5.8 for direct connections (Oracle databases), RDG support planned for early next year (RDG connections to Oracle DB still limited to 10 min at this time).

    Note that the system will still go down to 10 min when there is a large number of concurrent long-running requests as a safety measure.