DV Cache Created by One User Is Not Utilized Universally When Dataset Is Enabled For "Automatic Caching" (Doc ID 2701427.1)

Last updated on SEPTEMBER 27, 2021

Applies to:

Symptoms

On Oracle Analytics, DV projects are built on Datasets.  Automatic Caching option is enabled for the Dataset, which means the Dataset cache will be seeded in the first run and cache will be utilized in the subsequent runs of the DV project. It is observed that even though the cache gets seeded in the first run of DV project after dataset refresh, if another user logs in and runs the same DV project, it does not utilize the cache created by first user. 

Use case is detailed below:

1. Login to OAC and create a Dataset named "XYZ" based on RPD subject area.
2. Click on Inspect and edit the general tab to set Data Access as "Automatic Caching". Save the Dataset.
3. Created a DV Project named "DV_automatic_cache" based on the above Dataset. Grant Permission to BI Consumer and BI Author roles so that all users can access the project.
4. Log out.
5. Login as a different user say User1. Run the project named DV_automatic_cache.
Generated session logs show that query was being sent to the DB indicating that it did not hit any cache. It also shows that cache entry has been created (as the dataset is set for "Automatic Caching").
6. Now login as a different user with just BI Consumer role say User2. Run the DV project named DV_automatic_cache.
7. Session log generated shows that the query did not hit the cache. Instead it shows the query is being sent to the Database.

It is noted that when any user runs the DV project for the first time, the query is sent to DB and it consumes a lot of time since the cache is not being used.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.