Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 4532

Deadlocks on Logshipping Database Restore

$
0
0

SQL Server Version: 2012 (11.0.5343.0) 

We had a windows patching and servers were rebooted.We did take care of the disabling and enabling of jobs prior to the activity. LogShipping restore for databases are failing because of deadlocks and this deadlocks are caused by the background processes. When this background session runs on a database during restore, the restore job is identified as victim and it gets failed leaving the database in SINGLE_USER mode. When the background session completes its operation the next schedule of the DB restore is running fine.

Could you please suggest on how to fix this?

Here is the deadlock info for reference:

Deadlock-list
deadlock victim=process282c928
  process-list
   process id=process282c928 taskpriority=0 logused=10000 waitresource=DATABASE: 158  waittime=408 schedulerid=6 kpid=12568 status=background spid=41 sbid=0 ecid=0 priority=0 trancount=0
    executionStack
    inputbuf
   process id=process2f3c188 taskpriority=0 logused=10000 waitresource=DATABASE: 158  waittime=204 schedulerid=2 kpid=5848 status=background spid=42 sbid=0 ecid=0 priority=0 trancount=0
    executionStack
    inputbuf
   process id=process2946cf8 taskpriority=0 logused=10000 waitresource=DATABASE: 158  waittime=102 schedulerid=4 kpid=2536 status=background spid=22 sbid=0 ecid=0 priority=0 trancount=0
    executionStack
    inputbuf
   process id=process3722188 taskpriority=0 logused=10000 waitresource=DATABASE: 158  waittime=306 schedulerid=1 kpid=12528 status=background spid=17 sbid=0 ecid=0



Viewing all articles
Browse latest Browse all 4532


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>