OBIEE 11g: No Cache Hit For Dashboard Reports using the FILTER function
(Doc ID 1475433.1)
Last updated on JULY 08, 2021
Applies to:Business Intelligence Server Enterprise Edition - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
In OBIEE-11g the cache hit for our dashboards is extremely low. That is we are trying to seed simple answer reports without any filter (only time filter for week) is present. We seed the cache with it, but when the user runs a query adding another dimension filter (Department) even though the 2nd query result set is just a subset of the bigger query it does not cause a cache hit.
The “Primary Query” is the one that “seeds” the cache. The Child Query (with additional filters). Given that the Primary query result set is going to be a super-set, of the result set of the child query. Should not the Child Query cause a “Cache” hit and need not run against the database ? None of the notorious suspected cache breakers (like Pivots, excluded columns , Session Variable) are present in this report.
The child query does not seems to be hitting the “Primary Query” cache. Is this a product bug ?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document