OTBI query timeout should be increased

Neha Nahar

Organization Name

Persistent Systems Limited

Description

Currently as we are developing Learn reports for all reports if data is large in OTBI as well as BI report it gives timeout error.

The timeout time is 10 minutes , but in OTBI if we require more columns then it internally create query and gives timeout error.

Use Case and Business Need

For fetching large set of data  like past 1 year to 10 year data or some big range or criteria, Report should be exportable without using filters .

As this will be required in every organization to get for 1year or quater data .

But in current situation all our OTBI or BI reports failing for quater data also as columns are also more.

As OTBI we always drag drop columns and add as many columns and it internally creates query.

So idea would be :

1. Either increase timeout time

 

 

Original Idea Number: 83f8c34255

mgoswami

Hi Neha,

While Increasing the timeout from 10 minutes may help but would not resolve the issue. If you are working with large datasets involving many years data you may need to look at data warehouse options. The OTBI being built upon transactional system actually does larger database queries even if you try to get few columns. Also to note 10 minutes itself is a long time to wait for your analysis's result  increasing it further would only bring more wait and dissatisfied customers.

Please share if you have any specific scenario that need to be performance tuned.

Kind Regards

Brendan J. Doyle-Oracle

Hi there,

Thank you for your idea. I am relocating it to our Transactional Reporting (OTBI) Idea Lab for proper review: https://cloudcustomerconnect.oracle.com/resources/b2df648d2a/summary 

Best,

Brendan J. Doyle

drewP

I don't like the idea of having the user wait more than ten minutes. For us we have found the report will complete if scheduled.

I agree with the performance tuning comment but in the meantime, increasing the limit could help. Possibly an option for the user to click a button "Still there?" or have it as a configuration option though I think the time still needs to be a reasonable limit.