DQM Cache Issues with SAP BW Datasource

[IceTea]

Hi folks, i think we are running in a big caching issue...

In the first step, here the environment:

Cognos BI 10.2, SAP BW als Authentication Provider, SAP BW as DataSource. The Datasource is used with user-pass-through, so all queries are running with the logged-on-user-credentials and SAP BW Security is used. No configuration changes in configuration files (xqeodp.config.xml and bw.properties) where made.

Actually we have a Dashboard view with some prompt elements (dropdown- and picklists) which are filling some SAP BW Query Variables.  The data for these prompt elements comes from Queries on the SAP BW characteristics. This means, also the data in the prompt elements should be based on SAP BW security.

Here an example what we want:
- User A has rights to see all regions
- User B has rights to see only region Europe

- User A runs a report and sees data for all regions. Region-Prompt is filles with all regions.
- User B runs a report and sees data only for regoin Europe(filtered by SAP Security). Region-Prompt is filled with only Europe.

This is generally up and running, so we can say it works.

But we have mysterious caching effects.

The discussed behaviour could only be achieved if we delete DQM cache between the report runs from User A and B.

If we don't delete the Cache, the behaviour is like this:
- User A runs a report and sees data for all regions,  Region-Prompt is filled with all regions.(which is correct)
- User B runs a report and sees data for all regions,  Region-Prompt is filles with all regions. (which is wrong)

or

- User B runs a report and sees only data for europe, Region-Prompt is filles with only Europe. (which is correct)
- User A runs a report and sees only data for europe, Region-Prompt is filles with only Europe. (which is wrong)

In every Guide for DQM and SAP Cookbook it is described, that the DQM Cache is user-sensitive.

Example:
Security-Aware Caching
The caching logic available in Dynamic Query Mode is able, when connected tosecured metadata sources, to determine the secured access capabilities of eachuser as they access the data source. This information is then used to optimize thememory usage and internal representation of that user's secured view of the datasource metadata. Security can also be setup so that entire OLAP dimensions can beshared providing cache reuse and performance gains.

So, any hints about this issue?

Thanks in advance!

[MFGF]

Sounds very much like something you need to log with IBM's support desk! Not sure how many folks on here are using BW, but I'd imagine it's very few.

Good luck!!

MF.

[IceTea]

Thanks anyway, i found this:

http://www-01.ibm.com/support/docview.wss?uid=swg1PM76583

But i'll definitely open an issue at the IBM support... i'll keep you guys informed.

[MFGF]

Aha! So it looks like 10.2.1 fixes the issue.

Good find on the APAR! :)

MF.

[IceTea]

Hi,

i wanted to Keep you informed whats up.

IBM Support had a Suggestion to Change a governor in the FWM Model. But, this changed nothing.

Since then we wait for another Feedback. But while waiting, we installed 10.2.1 and it really seems that the bug is gone. Maybe i'll get official Information about this from IBM Support... but lets wait.