Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Deadlock Issue

Go to answer
Yeswa_Vaibhav_1
Level 6

‎25-06-20 07:24 AM

Hi All,

I am running my BOT suddenly after completing few records, BOT is terminating by showing the below error as reason: "Transaction (Process ID 335) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction" 
Process ID changes time to time, but issue is same and process is running on one VM only. No parallel process is happening. Can any one tell me it is occurring and how to handle this.

Regards

------------------------------
Yeswa Vaibhav Alwar Nerella
Associate Consultant
Capgemini
Asia/Kolkata
------------------------------
0 Likes
1 BEST ANSWER

Helpful Answers

Go to answer
chris.mcgowan
Staff
Staff

‎15-07-20 09:31 AM

Hi Yeswa,

When a deadlock occurs in SQL Server, two or more tasks are running simultaneously and holding locks on data. Then, each task requests to lock the data the other task is already holding. Both tasks wait for the other to give up, neither does. SQL Server could let this showdown continue indefinitely, but it won't. It picks one task – usually, whichever will be the least expensive to roll back – as the victim, and that task is killed.

To assist with raising this issue with support please could you speak to your Database Administration team and ask them to collect the deadlock information relating to this issue and provide this to support so they can investigate and help understand the issue. Collecting the deadlock information can be done by either enabling trace flags 1204 and 1222 or filtering the system_health Extended Events Session (Provided this is enabled) for "xml_deadlock_report".

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

View answer in original post

0 Likes
2 REPLIES 2

Go to answer
expertcr
Staff
Staff

‎02-07-20 06:47 AM

Hello Yeswa

To try to understand your issue we need more details about what is happening in your process, the selection log will help to review what you doing.
Also see how is the current stage of your DB, is this a test environment? only one bot and server?


------------------------------
Luis Lopez
Customer Support Engineer English and Spanish
Blue Prism Ltd
------------------------------
0 Likes

Go to answer
chris.mcgowan
Staff
Staff

‎15-07-20 09:31 AM

Hi Yeswa,

When a deadlock occurs in SQL Server, two or more tasks are running simultaneously and holding locks on data. Then, each task requests to lock the data the other task is already holding. Both tasks wait for the other to give up, neither does. SQL Server could let this showdown continue indefinitely, but it won't. It picks one task – usually, whichever will be the least expensive to roll back – as the victim, and that task is killed.

To assist with raising this issue with support please could you speak to your Database Administration team and ask them to collect the deadlock information relating to this issue and provide this to support so they can investigate and help understand the issue. Collecting the deadlock information can be done by either enabling trace flags 1204 and 1222 or filtering the system_health Extended Events Session (Provided this is enabled) for "xml_deadlock_report".

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