on 01-17-2011 10:57 AM
Hi All,
Is there a way that all the object locked in TCODE SM12 for over say 1 or 2 hours, gets unlocked automatically.
Any RZ10 parameter or via some other means.
I searched but couldn't get anything on the same.
Does anyone has some ideas on this. Please share, will be highly obliged.
Thanks & REgards,
Ashutosh
Directly there is no house keeping job to delete the locks.
One way is to maintain parameter rdisp/gui_auto_logout to say 2H (2 hours) so that, user session gets disconnected/logged off (if he/she is idle for 2 hours) and locks associated with the user must be reset. Just try and check
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Ashutosh
It would be a bad idea to auto cleanup locks in transaction SM12. Those locks have a purpose to keep your data consistent.
If you have issues that locks are set and cause issues for other users you should check where the locks come from and take action on it.
Setting different type of timeouts could help in some cases (as indicated above) to prevent users from leaving their screens in the middle of a transaction, possibly locking objects. User awareness can also help out (restricting reporting to the neccesary data and not requesting data from 10 years ago.
Do you currently have lock issues? If yes you can post on SDN to get some help on those.
Kind regards
Tom
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Regarding the parameter I was aware of this. But the requirement is like, sometimes when the user gets disconnected due to network blockage, then the material gets locked thought the user gets logged out.
It shows material is locked by user id "XYZ" though the id has been logged out. Under that situation I have to go to Tcode SM12 and manually delete the lock.
Is there a way out that the locked material gets unlocked automatically after certain time.
Thanks & Regards,
Ashutosh
Hello Ashutosh
It would still be a bad idea if it was possible.
You don't know up front that the lock stays because of a network disconnect or something similar. It could mean it would cleanup other locks that should not be cleaned up.
If this is a reoccuring problem, you should try and find the root cause of the fact that the locks remain (network issue or users that do not log off properly) and fix the root cause in order not to have those locks stuck in SM12.
Kind regards
Tom
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.