Showing posts with label OBIEE 11g query tracking. Show all posts
Showing posts with label OBIEE 11g query tracking. Show all posts

Sunday, 29 March 2015

OBIEE 11g query tracking mechanism


We had a requirement of tracking a query fired from OBIEE. This was to help us find out the Analysis that consume the most database resources.
It is possible that some user might be selecting a huge date range resulting in the problem at the database. So the trouble in this case might be the filters put by the user and not the Analysis itself.