Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 211 Oracle Analytics News
- 42 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 78 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
OTBI report working for a few users and not for many others with inconsistent behavior

Answers
-
Hi Shikha,
I assume this is the expected result with a database connection error message for a user that executes a query from a subject area for which they have not been granted the required role to use that subject area.
For this subject area
Payables Invoices - Trial Balance Real Time
to not get a database connection error
a user needs one of job role
- Accounts Payable Invoice Supervisor
- Accounts Payable Manager
- Accounts Payable Specialist
- Accounts Payable Supervisor
- Financial Analyst
- General Accountant
- General Accounting Manager
or a custom role with duty roles
0 -
Ooops - apologies but the image was quite small. I just read the message now later. I do not think it is roles now.
It says "Exceeded the maximum query execution time". So the issue is the query performance. It is taking too long to get your data. Are different users running it with different parameters. Can the user for whom it failed run it with more restrictive parameters to get less rows? Maybe just one invoice with a smaller accounting date range?
Review your usage tracking to see the different query text issued. Which ones fail and which ones have success. What are the where clauses? How many rows? Is it consistent slow or does it depend on other concurrent workloads? Can you get a repeatable test case.
Then view log in manage sessions. Try running the physical SQL(s) then comment in and out bits until you find which bit is the slow part causing the problem. You can use the explain plan in an adhoc data model to get insights.
0 -
Hi @Nathan CCC - Thank you for the response.
But one user is able to run this with the same parameter.
This is a report which shows open payables so it has got only one parameter of Accounting date.
The problem is some users with the same input get the output while others are getting this error.
Thanks,
Shikha
0