Categories
- All Categories
- 152 Oracle Analytics News
- 28 Oracle Analytics Videos
- 14.8K Oracle Analytics Forums
- 5.7K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 54 Oracle Analytics Trainings
- 12 Oracle Analytics Data Visualizations Challenge
- 4 Oracle Analytics Career
- 2 Oracle Analytics Industry
- Find Partners
- For Partners
How Does Automatic Caching Work with Row-Level Security in Oracle Analytics DV?

Oracle Analytics DV automatically caches the most frequently queried data to improve performance. However, if a dataset is sourced from a subject area with row-level security (RLS) applied, the query results can vary for each user.
Given that the dataset output differs based on user access, does the automatic caching mechanism still result in cache hits? Or does every user’s query create a unique cache entry, making caching ineffective?
Are there any best practices to optimize caching when RLS is involved?
Appreciate any insights from the community!
Answers
-
Please take a look into the following document especially 'About Cache Hits' which might be useful to understand the various scenarios.
Hope this help.
Cheers,
1 -
Additionally it depends on how the way 'Row Level Security' has been configured using semantic model or database.
If row-level security has been implemented in the semantic model, it provide some benefits like:
a) All the users share cache for better performance.
b) All the users share the same database connection pool for better performance.
etc.If it is done via, database using Virtual Private Database (VPD) feature:
Oracle Analytics query engine matches a list of security-sensitive variables to each prospective cache hit.
Cache hits will only occur for those cache entries which included and matched all security-sensitive variables.Please take a look into the following Oracle Note for more details.
Hope this help.
Cheers,
1 -
@Bhaskar Konar Thanks for sharing this. I will take a look at the shared documents.
1