SAP BW-IP no lock entries in RSPLSE

[Former Member]

Hello IP Experts

I have seen a lot of SAP BW IP installation and I am used to see locking entries in transaction  RSPLAN.

With this customer the locking entries are not shown  (TR RSPLSE / Tab locks).  Not surprisingly my colleague and me can plan at the same time the same thing.

Does anyone have a good idea? Why?  At the end I like to get back the locking functionality .

Here some detail information:

• - Bex Query row is set on  lock relevant
• - I have set up relevant characteristics for lock up (RSPLSE)
• - Lock table is ‘shared object memory of server
• - In expert modus, the  ‘no locks’ flag is not set
• - I see the lock entries in transaction SM12
• - SAP_BW 730 / Level 0005
• - Oracle

Thanks  a lot for some hints and ideas.

Best regards

Christian

[cornelia_lezoch · Accepted solution]

Hi Christian,

funny thing,

my users would love to have that "functionality"

So I would really like to know how you managed to get this.

Are you sure you can plan the same values and safe them? If you both safe - is there a difference between the data records?

Are there any navigation attributes used as lock characteristic?

Is 1KYFNM used as lock characteristic?

Is the cube set to plan relevant?

Are you looking for the locks of an info cube or dso?

regards

Cornelia

[cornelia_lezoch · Accepted solution]

by the way - what happens if you use no lock relevant char - then the whole cube should be locked - does this work?

[Former Member · Accepted solution]

Hello Cornelia

This functionality is possible with the  ‘no locks’ flag, in TR RSPLSE in the first Tab and you have to write 'expert' in command field.

BUT is strongly not recommended.

[cornelia_lezoch · Accepted solution]

but you wrote that you have not set this flag

[Former Member · Accepted solution]

Yes, thats right

In a test environment it could make sense to use the 'no lock' flag, where so the locking mechanisme is stopped

Thus I checked in my production environment, if that flag is set. It is definitively not set and the locking mechanisme is still not working.

[cornelia_lezoch · Accepted solution]

is it not working for any of your cubes?

did you check on the topics that I listed above?

what happens if you create a new cube, put just one small aggregation area on top cretae a query ... does it produce a lock?

[Former Member · Accepted solution]

Hello Cornelia

Yes I have tried

- with another data model,

- taken out all locking relevant characteristcs, moved back again

- have build a new small aggregation level

- 1KYFNM is not set as locking relevant

- Cubes are planning enables. In addition I saved data and my colleague changed then my data  almost at the same time

- I checked the locks for the cube. But I get confused so I went through all data model elements ( aggregation level, multiprovider, infocube) to see if there is a lock entry

.. in result no lock entries

It is totally against, what I have learnt in SAP IP a couples of years ago.

Best regard

Christian

[cornelia_lezoch · Accepted solution]

Hi Christian,

I think you need to use 1KYFNM as lock relevant

if this does not work, check wether the system is creating any lock at all - do the following

1. open rsplse
2. go to set lock characteristics for a certain cube, go to change mode
3. leave it in change mode open
4. run a query wich is planning relevant and data entry enabled
5. you should get an error message that the system is not able to create locks

if you do not get this message, then there is something wrong with your lock sever, then I suggest you contact SAP via OSS

regards

Cornelia

[gregor_dieckmann · Accepted solution]

Hi Christian,

7.30, SP05 is really old. It seems to be an very old problem with FB ENQUEUE_READ used in the BW enqueue server. Please check notes:

1672515

1602244

Regards,

Gregor

[Former Member · Accepted solution]

Hello Gregor

Yes it helps and solved the isseu...and yes we are on an old 7.3 😞

Thanks and best regards

Christian