Question
5
Replies
2599
Views
DXC Technology
Posted: May 23, 2018
Last activity: May 31, 2018
Closed
Requestor already has the lock
Dears,
I have a particular entry in pr_sys_queues whose content when checked it says that it is due to another requestor already has the lock.
Cannot obtain a lock on instance XXXX-WXX-CX IFM-698636, as Requestor BF80544A1738726E72AA5665F5A602E51 already has the lock
But i am unable to find such a requestor in the AllLocks page.
Due to which the entry in pr_sys_queues goes on retrying now with this message.
How is this possible. Share your inputs.
regards,
Jagan
The requestor ID starts with a B so that means it is a batch requestor or agent that has the lock. How is the queue item created? Are there other agents or batch processes that would be processing the item?