Hello All,
PROGRESS Version 9.1E04
We could see exclusive lock on many tables from a user, which logged out yesterday.
Users facing issue while accessing those records. Suggest me how to release those locks.
Thanks,
Karasanr.
> I used proshut list
So the process is still exist in the _Connect VST but with the "usertodie" flag (_Connect-Disconnect eq 1).
> can we release the lock if we kill the PID from OS level.
Was it a self-service client? One of two possibilities: the lock will be released or db will crash.
Get its protrace file (kill -SIGUSR1 <pid>) before you're going to kill the process.
> a user, which logged out yesterday
How did you check this? promon/User Control or _Connect VST?
How did you check this? promon/User Control or _Connect VST?
I used proshut list and promon to find the user & lock details
Thanks,
Karasanr.
Thanks for the suggestion George. I am able to find entry for the user in _connect but not in promon and proshut list utility.
can we release the lock if we kill the PID from OS level.
Thanks,
Karasanr.
> I used proshut list
So the process is still exist in the _Connect VST but with the "usertodie" flag (_Connect-Disconnect eq 1).
> can we release the lock if we kill the PID from OS level.
Was it a self-service client? One of two possibilities: the lock will be released or db will crash.
Get its protrace file (kill -SIGUSR1 <pid>) before you're going to kill the process.
Below is the entry in _connect for this user
79 SELF mfgadmin /dev/pts/8 Thu Oct 19 14:26:33 2017 29871 ? 0 -- 1724709937 82 0 1│
│ 0 0 0 No
It is self-service client .
Thank you for your inputs
Thanks
Karasanr
Does the process with PID 29871 still exist on OS level?
What promon/R&D/3/2 (I/O Operations by Process) reports about Usr 79? Wait a few seconds then update statistics (type "U" and press Enter). Will you see the changes in statistics for Usr 79?
What promon/R&D/1/4/3 (Active Transactions) say about TRID 1724709937? When it was started? And when the process was disconnected from database? Grep db log by " 79 " or by "29871".
Sorry, We killed the process from OS end.