Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 211 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 77 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
OAC Auto Cache Purge
Oracle Products :
Oracle Analytics Cloud (OAC)
Specific Business Problem:
In the analytics data warehouse, new data is incrementally loaded from its source into the data warehouse. It's imperative that this fresh data seamlessly reflects on Oracle Analytics Cloud (OAC) reports without requiring manual cache clearance for each report or dashboard by users. Regrettably, OAC lacks an automated cache purge feature, compelling users to resort to various workarounds. This absence significantly undermines data consistency, posing a considerable challenge for businesses relying on OAC reports. Therefore, the integration of an auto cache purge functionality within OAC is deemed essential for ensuring smooth utilization of its reporting capabilities.
Business Benefits :
The implementation of an auto cache purge feature in Oracle Analytics Cloud (OAC) would yield several key business benefits for users:
Enhanced Data Accuracy: With automated cache purging, users can rely on up-to-date data reflecting the latest changes from the data warehouse. This ensures that reports and dashboards accurately represent the current state of the business, leading to more informed decision-making.
Time and Effort Savings: Eliminating the need for manual cache clearance streamlines workflows for users, saving significant time and effort. Users can focus more on analyzing insights rather than performing repetitive administrative tasks, ultimately increasing productivity.
Improved User Experience: Seamless integration of fresh data into OAC reports enhances the overall user experience. Users can access reliable, real-time information without encountering discrepancies or delays, resulting in higher user satisfaction and engagement with the platform.
Faster Decision-Making: Timely access to updated data empowers users to make quicker decisions based on the most current information available. This agility in decision-making can provide a competitive edge, especially in fast-paced industries where rapid responses are critical.
Greater Confidence in Reports: By ensuring data consistency and accuracy, the auto cache purge feature instills confidence among users in the reliability of OAC reports. Users can trust that the insights derived from OAC are dependable and reflect the true state of the business, strengthening their confidence in strategic decision-making.
Overall, the introduction of auto cache purge functionality in OAC would not only optimize data management processes but also significantly enhance the value proposition of the platform, driving better business outcomes for organizations leveraging its reporting capabilities.
Comments
-
needed feature for OAC
0 -
You can follow below document for the solution to this requirement -
How To Programmatically Clear Cache in Oracle Analytics Cloud(OAC) using JDBC [Video Content] (Doc ID 2956513.1)
1 -
As mentioned in the problem definition above, there are multiple workaround (for which OAC support is not provided, mentioned in the document as well) but the ability to auto purge should be available as part of seeded OAC feature, users should be able to decide the time when they want to schedule the purge without intervention of IT via any backend changes/workarounds.
Hope it helps clarify the need for this feature.
Regards,
Manu
0 -
I agree that, we do not have any in built feature to schedule the cache purge automatically.
That is why we are providing the BI-JDBC driver based tool to connect to OAC server via java program (the utility mentioned in above KM - 2956513.1) which you can schedule as a cron job.
0 -
This post is requesting the feature to be made available as part of the seeded product in next releases.
Reg, the workaround, not just the doc, but there are numerous other workarounds available. The customers need ability to schedule themselves via a front end feature rather than depending on IT for backend workarounds. Hence the need.
Hope this clarifies.
1 -
@Manu R-Oracle which assets do you want purge. Subject Areas tables for example allow you to configure caching rules/behavior. For example, datasets and OAC data flows allow you to schedule reload/runs. There are lot of assets in OAC and it is not clear which you want to control.
Can you add some details on the types of assets you want to manage this way?
0 -
@Bret Grinslade - Oracle Analytics-Oracle The need is to purse all the OAC classic subject area , Dashboard , Reports cache at scheduled time daily. The subject area cache option just gives ability to enable/disable. It does not have a control/ability to schedule at designated time. Hence the request for this feature. Hope this information helps.
0 -
@Manu R-Oracle You are not right. In metadata (RPD) you can define for physical table object frequency of cache purging (purging of BI Server cache entries, connected with this physical table). But I understand, that this is in majority of cases not what you want. Usually you want to purge BI Server cache entries, when your data has changes (ETL process has refreshed them for example). And for those cases you would leverage those JDBC calls for BI Server cache purging. What I am more missing - @Bret Grinslade - Oracle Analytics-Oracle - is control over BI Server cache entries, connected with DV data sets - for those, there isn't any settings (like disable BI server caching for particular data set) or there isn't any ODBC/JDBC call, which allows me to purge BI Server cache entries connected with particular data sets. There is definitelly space for improvement here.....
0 -
@Michal Zima - Please note, you talking about the 'Cache Persistence Time' at individual table. The request is for purging cache at server level not at table. Hope you have understood the need and feature requested here now. As I mentioned above, JDBC call is just one of the backend workaround, there are others too. But you might know, the customization in workarounds are not support by product team as clearly mentioned in the JDBC setup document.(Doc Id 2956513.1) Hence the need for a seeded product feature.
1 -
@Manu R-Oracle Having some "global" setting for "Cache Persistence Time" (at OAC/OAS instance level) does not make much sense for me. Usually (I am talking about our "usage", but I am sure, that we are not the exception) you "mapped" for reporting (either in RPD or in data sets) different data, which have different "volatility" (are refreshed with different frequency ate different time) and thus purging all cache entries in the same time is not what you want. But your scenario might be different.
0
