Is there any way to identify which transaction/class took the lock the record when we get this UNABLE_TO_LOCK_ROW issue.

Simply giving UNABLE_TO_LOCK error and not giving the idea about he potential transaction which caused lock is not helpful to rectify such issues.

Is there any way by which we could be able to identify which transaction/user/classes/processes are taking the lock?

  • 2
    No, I'm pretty sure you're out of luck. – Adrian Larson Nov 13 '17 at 21:03
  • ohh...I thought so, its very annoying even though you get the error, but you can't confirm whether any of your optimization has really fixed the issue or not. :( – Kiran Machhewar Nov 14 '17 at 3:02

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.