topic RE: Deadlocks usually indicate a… in Product Forum

Transaction (Process ID xx) was deadlocked

MarleenHordijk — Tue, 23 Apr 2019 13:48:00 GMT

Can somebody help us with this error? We read a lot about this online, but we don't understand it because English is not our first language. Can somebody explain this very simple? Transaction (Process ID xx) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. We run the processes trough the control room. This always goes ok, but last Friday we had 3 processes with these errors. Not on the same time of the day. Thanks.

Deadlocks usually indicate a…

John__Carter — Tue, 23 Apr 2019 14:19:00 GMT

Deadlocks usually indicate a database performance problem http://portal.blueprism.com/customer-support/support-center#/path/11373…

Can anyone advise How toâ€¦

MythiliR — Tue, 28 May 2019 15:26:00 GMT

Can anyone advise How to resolve ? and why does it come?

RE: Deadlocks usually indicate a…

BernardoGonçalv — Thu, 05 Nov 2020 11:22:00 GMT

Hi John,

The link does not seem to be working.

Could you please explain what kind of performance problems we need to look at in order to address these issues?

------------------------------
Bernardo Gonçalves
------------------------------

RE: Deadlocks usually indicate a…

Yeswa_Vaibhav_1 — Fri, 06 Nov 2020 06:34:00 GMT

Hi John,

I am also facing this deadlock-issue more often, Could you please suggest how to diagnose the issue.
Also the above link doesn't have any doc's in it. Kindly share the new one.

------------------------------
Yeswa Vaibhav Alwar Nerella
Associate Consultant
Capgemini
Asia/Kolkata
------------------------------

RE: Deadlocks usually indicate a…

John__Carter — Fri, 06 Nov 2020 08:50:00 GMT

Sorry guys, try this link.

------------------------------
John Carter
Professional Services
Blue Prism
------------------------------

RE: Can anyone advise How toâ€¦

chris.mcgowan — Fri, 06 Nov 2020 13:16:00 GMT

Deadlocks occur when two (or more) sessions cannot proceed because they hold mutually incompatible locks on the same resources. SQL Server handles deadlocks internally and resolves them by killing the transaction with the least deadlock priority or the one that has done the least amount of work. I recommend that you speak to your DBA team to ascertain what queries are involved in these deadlocks, collect as much information as you can and raise a support ticket so we can assist you.

The below link is extremely useful in identifying and resolving deadlocks, it should assist your DBA team with your investigations.

https://www.brentozar.com/archive/2017/12/introducing-sp_blitzlock-troubleshooting-sql-server-deadlocks/

Regards

------------------------------
Chris McGowan
Senior Technical Consultant
Blue Prism
------------------------------