Error running OTBI report - The user request exceeded the maximum query governing execution time.

Question

There is an OTBI report which gives results when I run using my ID but the same report is giving error - "The user request exceeded the maximum query governing execution time" when we try to run via another user ID.

We have also added all the respective subject area duty roles.

Please suggest why are we receiving this error.

RVohra · Answer

@Arti Gupta-Oracle ,

There isn’t enough context or detail provided to fully understand the issue. Please share more information about your report, which environment, the module/products involved. This will help others give you a more accurate answer instead of making random guesses. Appreciate it!

Rich Merkel · Answer

What subject area are you using?

Admin users will have query run much more quickly, as the security layer is not applied.

When users have role to access, there is additional overhead to check security layer.  For example I have admin role, user has project accountant role.  Query will not complete runs over 10 minutes, but admin user runs in two minutes.  This is for good reason as security is very important for non-admin users.

I have found that you need to optimize you query further.  For example project costs - actual cost real time, if using a date/accounting period filter, you must use accounting date under folders Expenditure Item and Cross Distribution Details → Expenditure Item and Cross Distribution Record Information → Accounting date as compared to accounting date in fiscal year folder.

In some cases I created Oracle SR to help me optimize by providing nqquery logs.

When some analysis exceeds maximum time (around 9-10 minutes), for non-admin user you will need to optimize the analysis.

Aarthi Natarajan-Oracle · Answer

Hi Team,

I am no expert but based on my experience, i have faced this issue when i have added lot of columns in criteria and then when i try to view the graph, it gives me this error. So, when i remove unwanted additional column save and then click on results, it doesnt give this error.

But @Abinaya, your case is bit different where you are saying you are not facing this issue but another user is, then please compare the roles between you both and try to add the missing roles and see if that might be helpful?