Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 16 Oracle Analytics Lounge
- 216 Oracle Analytics News
- 43 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 79 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Report very slow after adding one filter

Hi All
I have a report which works fine until I need to add a filter on one field. I have added Not in filter for one value and it gets so slow that it does not open at all after 30-45mins I have to kill the request from EAS Console. I have also tried to use Equal/in criteria for the same dimension leaving the Value I don't need but that does not change anything. Is there some setting or something I need to do or anyway I can troubleshoot what could be happening? Any pointers? Appriciate any help on this.
Thanks
Suresh
Answers
-
You mention EAS but that is all. What software are you using? What version? What platform? What data?
0 -
Of course would be good if you can give some details (all what @rmoff mention and everything else you can).
What I guess is that your source is Essbase, so it's a MDX query, without filter it works fine and with the filter it doesn't ...
Can you compare the MDX with and without filter? Does it makes sense?
Did you consider having an issue with your cube?
Would be good if you can analyze the details of what happen so you can put in place a proper solution, as workaround waiting to make it the right way can you maybe use Selections Steps to "hide" the info you want to remove from the screen?
0 -
Yes My source is Essbase version 11.1.2.3.500 and OBIEE 11.1.1.9. Is there a way to see MDX query from OBIEE that is send to Essbase so I can compare? I have used member in selection to hide and it improved retrieval bit.
Thanks,
Suresh
0 -
If you go in the Administration page of OBIEE and Manage Sessions from there you see the logs. In case you see only the logical SQL you must increase a bit the log level to see the physical query as well, in your case MDX.
And also in the nqquery.log file.
0