Graham A

24 Jun 2014 8:31 AM

When I run the update_rollup_mom_db.sql update script I get the following error:

Msg 1205, Level 13, State 56, Line 1
Transaction (Process ID 105) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Msg 3727, Level 16, State 0, Line 1
Could not drop constraint. See previous errors.

On the initial run it showed a number of row affected as you describe, and was immediately followed by the error above. On subsequent runs the error appears by itself.
I have tried stopping the SDK service on all monitoring servers (23 of them) but the deadlock is still present.
Can I proceed with the last stages of the UR5 update - datawarehouse and management packs - or must this be rectified first?
We are doing this as a stepping stone to going to SCOM 2012 R2.

Thanks
Graham

Ashish Vikram Singh

24 Jun 2014 8:42 AM

Hi Kevin, your post is very informative. Thanks a lot for sharing it and keep it up.

Kevin Holman

24 Jun 2014 1:07 PM

This needs to be rectified. The SQL script must complete. I have not seen this have an issue when the HealthService is stopped on all management servers... there should be zero database connectivity. An additional step is stop/bounce the SQL service to break any existing procedures running. 23 management servers? That's quite an interesting environment!

Graham A

25 Jun 2014 12:30 AM

Thanks Kevin. That worked.
Yes it is an interesting environment which also includes 6 gateways.
Our test environment has 4 management servers and didn't have this issue.
Thanks again for your help.

SCOM Newbie

9 Oct 2014 8:28 AM

IF I will to compare UR3 and UR5 and UR7, what is or are the reasons why I should rollup and which is better to use for our current version SCOM 2012 SP1 UR3 and most of our servers are Windows 2012. Another question is if I will roll up and I am having issues managing Windows 2012 R2 servers which upgrade path should we take?

Thanks in advance for your help.