Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 208 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 76 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Obiee Cache Question
Hi,
In our company, we use obiee 12. There are lots of dashboards and analysis seen by customers. Sometimes, because of obiee cache reports are not refreshed and does not bring latest value.
How can we solve this issue? We thought that we can clear total cache every 6 hours :S Is it a good opinion? Or, do you suggest any other idea?
Thank you for your help.
Regards,
Dilek
Answers
-
Hi Dilek,
This is what you get with cache: before to enable cache, one must have a cache management strategy in place.
Turn off cache and no problem anymore. If you want to keep cache on, you must define a process fitting into your current processes and workflow, depending on the sources etc. to define when and how to purge cache.
0 -
Thank you. Turning off cache is not a solution of course But since I do not know the correct way, I just want to learn how to go on. Here, I understand that deleting cache 6 hours apart is ok for us. That should be our process Right
0 -
Alternative approach:
Add a SQL prefix to all the analyses which are being sent out: "SET VARIABLE DISABLE_CACHE_HIT=VALUEOF(NQ_SESSION.CACHE_HIT_FLG)";
Then simply create a session variable CACHE_HIT_FLG which you set to 1 or 0 depending on who runs the analysis - i.e. whether it's being sent out or kept internally.
Done. Easy as pie.
0 -
dileraco wrote:Here, I understand that deleting cache 6 hours apart is ok for us. That should be our process Right
If 6h is the answer, then go for 6h
In general you start looking at the sources you use for the analysis, you identify how often those changes and get the business owner deciding if they always want to see the fresh data as soon as possible or are happy to have a delay. Based on all the answers you can decide the best strategy: do you purge cache on the BI side at a fixed schedule? Or do you get the source to trigger the purge of the cache?
Many add a purge cache step to their ETL: when all the data is refreshed it's time to purge the BI cache so people see the freshly loaded data. As the ETL is the one knowing when it's over, adding a step there is also a good practice.
There isn't a good or bad way, there just is a worse or better way for your own use case, and you can also have multiple cache management strategies in a single OBIEE. Different rules for different subject areas.
And obviously also what Christian suggested: this is a "per user" approach with users having cache and others not having it.
0 -
Gianni Ceresa wrote:And obviously also what Christian suggested: this is a "per user" approach with users having cache and others not having it.
Per user, per app role...anythng you want
0
