Problems with cache

[OV]

Hi everybody,

I am having some problems with the reports being executed against the warehouse instead of the cache. This is what I did:
I created a user that has no security filter. The user has full control over the reports that he is running.
Then I set up the following:
Under Project Properties/Caching/Cache prompted and cache unprompted reports are checked.
Under My preferences/ Advanced/Use server cache is checked
On the web, Under General/Refresh/Retrieve data from the latest valid MicroStrategy Server cache is selected.
Yet even if the user just refreshes the report that he just ran, it queries the database instead of the cache.
I believe that the problem is somehow related to security because if I go under user privileges/Administration and check "Bypas all object security checks", then the reports start hitting the cache instead of the database.
Does anyone have any experience with this kind of problem? Thanks in advance.

OV

 

[omarmtz]

Do you check the security privilege of the user/group, in Administration/User Manager/ selecting the user/group and Grant access to projects... and in the 4. Common Privileges/Use Server cache???

By default this is unchecked.

I hope this helps.

 

[OV]

The user has access to the project and full controll over the reports that he is running and in common privileges/"use server cache" is checked

 

[nlim]

how do you know the reports are running against the warehouse?

I'd troubleshoot along the following lines

1) clear all report caches
2) log in as administrator and run the report
3) make sure the report is now in the cache monitor. The cache hit number should be 0.
4) log in as the user. Run the same report. log out
5) log in as admin, check cache hit for the report. see if it is increased.
6) if the user is creating a new report, there's no caching until it is saved.

 

[OV]

Thanks for your help. I have done all the steps above and more.
I know that the report is running against the warehouse because I can run a trace on the database and see queries that are being run.

 

[nlim]

You will need to get more granular then...

1) isolate if it's a general permissions issue.
- login as user, create a new metric M1, and create a new report R1 with M1 and one attribute A1.
- see if R1 is run against cache when user executes it a second time.
- if no, then try R1 with another attribute A2. Make sure that A2 is full control by user. If still no cache hit, it's a general permission issue; call tech support.

2) isolate which is the offending report component.
- if step 1 uses cache, then something in your admin-created report (let's call it R2) is causing it to not use cache.
- in the version of R1 above that uses cache, switch M1 with each of your metrics in the R2. See which metric triggers the DW run.
- in the version of R1 above that uses cache, switch A1 with each of the attributes in R2. Same thing, see which attribute causes DW run.
- in the version of R1 above that uses cache, add each of the filter condition in R2.

you should be able to identify the problem causing component.