BI-IP: Every time the whole Real-Time Cube is locked

[Former Member]

Hello everyone,

we have configured locking-characteristics in /nRSPLSE for our aggregation level.

However each time a user A opens and enters data the whole underlying Real-Time-Cube is locked completely. Instead only a certain number on which user A

is about to enter planning data should be locked the rest of the numbers should be available to other users.

Has anybody an idea to solve this?

Did you use locking in BI IP already ?

Thank you,

Daniel

[Former Member]

You should create a filter in data modeler and then use this filter in you query, then the query should only lock the data for user A.

[Former Member]

Hi Daniel,

where do you experience these locks, in the planning modeler or in the analyser? We have a same issue, but only with the planning modeler. when working in parallel in the analyser we don't have this issue. We posted this on OSS. I can keep you posted

D

[Former Member]

Hello Dries,

these locks appear when some person A is planning in the web.

It's just like person B is not able to plan anything during that time.

Regards,

Daniel

[Former Member]

Hi Daniel,

all our locking problems have been solved by implementing SP 13. Perhaps you should try the same. In SP12 we also experienced a full lock of the infoprovider from the moment someone was planning on only a fraction of it.

Dries

[gregor_dieckmann]

Hi Daniel,

nothing was changed in the lock management in any support package. The problem usually comes from the fact that you are using restrictions only in the default values, not in the filter of the query.

Only the restrictions in the filter of the query will be locked, the default values only determine the initial view of the query. If you model something in WAD that changes 'selections' make sure that you change the filter values of the query not only the default values.

Regards,

Gregor

[Former Member]

Hi Gregor,

thank you for your answer.

I am still searching for the root of the problem since we don't use restrictions in the default values of the query but only in the filter of the query.

Regards,

Daniel

[gregor_dieckmann]

Hi Daniel,

then check the lock relevant characteristics in RSPLSE. By default every characteristic is lock relevant, i.e. can be seen in the right table of the second tab in RSPLSE. Maybe you have changed this.

Some people were confused by this setting and put some characteristics into the left table, but this table is for the not lock relevant characteristics (i.e. these characteristics will always be locked with *, i.e. the all member).

Regards,

Gregor

[Former Member]

Hello Gregor,

thank you for your answer.

This forum is really a great idea!

What you are describing indeed might confuse some people.

In my case the problem had to do with navigation attributes.

You can mark them lock-relevant using ta expert in rsplse.

Regards,

Daniel