Skip to Content

Locks not released after timeout

Nov 02, 2017 at 03:08 PM


avatar image


we are using Lumira designer 2.0 and we built a planning application based on BI IP functionalities. It works very well but we have an issue with locks.

When a user is connected he enters planning data in lumira (Locks are generated). If the user doesn't disconnect properly, timeout occurs. The issue is that timeout doesn't release session nor locks in BI IP. Consequently, if the user XYZ tries to reconnect to the application, a error message is raised saying that data is locked by user XYZ...

Have you any workaround to propose to solve this issue ? I only saw oss notes to allow to increase timeout.



10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Tammy Powlas
Nov 02, 2017 at 03:30 PM

I think you are right about increasing the timeouts; have you tried that? Can you trace what is going on in the backend?

Show 3 Share
10 |10000 characters needed characters left characters exceeded

Hi tammy

thanks for your answer.

Regarding timeout, it is more a workaround because it seems to be a bug in Lumira/DS. Timeout should release session and locks. Regarding trace, I don't know where to search. All I see is that when a user has a timeout, session is still there in SM04 (BW) and locks in SM12 are still there as well.

Best regards



I mean activating a trace on the BW backend...I think the transaction is ST01 or ST05?



I will ask our BW colleague then


Sai Kumar Konka Nov 14, 2017 at 01:05 AM

Hi Gabriel,

I have raised an issue with SAP 2 months ago - planning locks not getting released on two occasions

1. On cluster environment (we have two servers) - SAP found the issue and releasing fix in Lumira 2.1 , please refer note 2556678.

2. Planning locks are not getting released when BO sessions expires - this is still being investigated by SAP.

Below is the email from SAP - I am hoping 2.1 will fix both the issues.

Good Morning Sai

The processor has updated the incident and has attached Note 2556678 detailing the fix related to planning locks not being released in a clustered environment.

They are currently investigating the issue of planning locks not getting released when a session expires.

10 |10000 characters needed characters left characters exceeded