I have a report that has a few filters on a couple of columns there. One filter is on the measure "Account open Amount" as not equal to 0. When I run the report and check the SQL generated, I don't see "Account open Amount" <> 0 in the where clause of that SQL. I do see all the other filter conditions appear in that where clause. The measure has a Sum aggregate rule applied to it from the BMM layer
Is it an expected behavior of OBIEE?
I have a similar OBIEE problem where my date filters dont get included in the Physical query send to the database.
The request takes too much time since it brings all the data back in cache.
Please let me know if there are any tricks to make OBIEE server to include my date filters,
Thanks in advance,
verify if feature 'HAVING_SUPPORTED' is checked on Physical Layer -> Database Properties -> Features.
If database dows not support having then the BI server will make the filter on your aggregation...
If database support having than the BI server will pass the filter to database for better performance...
Hope this helps...
Yes Nicolae 'HAVING_SUPPORTED' is checked.
I checked nqsquery.log my request gets stuck at the database query.
Even the session log shows that the report is stuck at database query.
But when i run that same query in db2 database it runs in 4 mins max.
Please let me know if i have to set anything for the database query to return faster. I tried increasing the cache but its not working.
Thanks in advance,
When I include a measure in filter section (for eg: sale_amount > 10000 ), while having marked the measure with default aggregation as SUM in the BMM layer of RPD, I see the filter gets applies on the aggregated value. ie, the filter is applied after aggregating the sale_amount. But the requirement is to filter and then aggregate. To accomplish this, I do not want to expose sale_amount two times in the presentation layer (once with aggregation enabled in BMM and another without aggregation), as this will confuse my power user community.
How can this be done?