When running UR#1 for SCOM 2012 R2 you have to run a SQL query against the OperationsManager database. Many times this query throws an error, like this one:
For what I’ve seen this issue happens 9 out of 10 times this update is applied. So even when you’re SCOM environment is relatively small, changes are you bump into it. It’s caused by the fact that other processes have locked certain resources in the SCOM database.
Solution 01 – Quick & Dirty
This isn’t a very nice approach since you shut down the SQL Server service of the SQL server instance hosting the OperationsManager database. This might cause some unwanted side effects like:
- A corrupt SQL database (in the most extreme case);
- When that SQL server instance hosts other databases related to other applications besides SCOM it will create issues for those applications.
Solution 02 – The Decent Way
This approach takes more time but works far more better. No nasty side effects here:
- On ALL SCOM Management Servers stop de System Center Data Access and System Center Management Configuration services;
- When present, stop the Correlation Engine (related to the Exchange 2010 MP) (Nice one Kevin!);
- Rerun the query again.
Additional information about this SQL script
The related KB article states that the SQL script is meant for the Data Warehouse database but should be run against the OperationsManager database:
But don’t let this (bad) English fool you: This SQL script is meant SOLELY for the OperationsManager database!