Hi, After moving the OpsDB to a new server i followed Kevins blog and Microsoft KB on how to do it Everything worked fine except i get the following error: Alert Monitor: Partitioning and grooming has completed recently Description: The partitioning and grooming processes for the operational database (OperationsManager) on the server OLDDBSERVER.ourdomain.com have either not been run recently or have been failing. At the time this alert was raised, the partitioning and grooming process had not completed for days. The thing is that the Alert is pointing to OLDDBSERVER, how do i redirect so it knows where to find the new DB? Everything else seems to work fine, everything is green and i get alerts as usual. Because of this Alert i am getting nervous that my grooming is not working correctly, any tips how to check this?/Maekee

Can you check this: OperationsManager: Stop the Operations Manager services (System Center Management, System Center Data Access, and System Center Management Configuration for root management servers, and System Center Management for management servers) on the management servers in the management group. In a clustered root management server environment, use Cluster Administrator (Windows Server 2003) or Failover Cluster Management (Windows Server 2008) to configure each of the three services listed above with the Take Offline option. Update the registry on each management server in the management group to reference the new SQL Server-based computer. Complete this step also on the root management server. If the root management server is clustered, you must complete this step on all the nodes in the cluster. Note Before editing the registry, follow your site's backup policies with regard to the registry. a. Log on to the management server with Administrator permissions. b. Click Start, select Run, type regedit in the Open box, and then click OK to start Registry Editor. c. Under HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Setup, double-click the value DatabaseServerName, and then change the value to the hostname of the SQL Server-based computer now hosting the OperationsManager database. If you are using a named instance of SQL Server, be sure to use the ServerName\Instance name format. d. Click OK. e. Close the Registry Editor. f. After you have completed this step on all management servers in the management group, restart the System Center Management, System Center Data Access, and System Center Management Configuration services on the root management server, and then restart only the System Center Management service on the remaining management servers. Update the OperationsManager database with the New Database Server Name, and ensure that the account that you are logged on with has sufficient privileges on the SQL Server instance. a. Open SQL Server Management Studio. b. Expand Databases, OperationsManager, and Tables. c. Right-click dbo.MT_ManagementGroup, and then click Open Table if you are using SQL Server 2005 or click Edit Top 200 Rows if you are using SQL Server 2008. d. Change the value in the SQLServerName_6B1D1BE8_EBB4_B425_08DC_2385C5930B04 column to reflect the name of the new SQL Server-based computer. e. Save your change. See also the Operations Manager 2007 R2 Operations Administrator’s Guide (Page 117,118,119,120,121) To see how grooming is doing you can also use this SQL Query: SELECT * FROM PartitionAndGroomingSettings WITH (NOLOCK) Certifications: MCSA 2003|MCSE 2003|MCTS(4*)| MCTIP:SA

Hi Shadowman123, This is exactly the steps in the guide from Microsoft. Re-did them again to check that the values in the registry are correct and they are. If they pointed to the wrong OperationsManager DBServer i think i would get alot more errors than just this monitor? How do i know if the Partitioning and Grooming are running like they should? So, back on square one.. anyone?/Maekee

See the last line in my post: To see how grooming is doing you can also use this SQL Query: SELECT * FROM PartitionAndGroomingSettings WITH (NOLOCK)Certifications: MCSA 2003|MCSE 2003|MCTS(4*)| MCTIP:SA

Yes, i get the results.. but how do i know if the Partitioning and Grooming are running like they should? Should they be updated daily? or how often is accepted?/Maekee

There is value called GroomingRunTime, and there should be the last day, so in this case 2010-11-14. Should be updated daily. There runs a stored procedure every night which is called p_PartitioningAndGrooming. See also here for more information about the Grooming process. Grooming process in the Operations Database In my own enviroment it shows this for example: GroomingRunTime 2010-11-14 23:10:25.960 2010-11-14 23:10:25.960 2010-11-14 23:10:26.243 2010-11-14 23:10:26.323 2010-11-03 23:08:48.470 2010-11-14 23:10:26.883 2010-11-12 23:10:04.663 2010-11-11 23:10:12.050 2010-11-14 23:11:04.783 2009-09-11 00:00:00.000 2010-11-14 23:11:04.793 Certifications: MCSA 2003|MCSE 2003|MCTS(4*)| MCTIP:SA

This is from my GroomingRunTime (Ran this now) 2010-11-12 23:03:40.643 2010-11-12 23:03:40.643 2010-11-12 23:03:40.840 2010-11-12 23:03:40.997 2010-11-12 23:03:45.910 2010-11-12 23:03:45.923 2010-11-10 23:11:11.087 2010-09-10 22:08:11.403 2010-11-07 23:11:06.170 2010-08-18 22:07:58.777 2010-11-12 23:03:45.930/Maekee

This is from my GroomingRunTime (Ran this now) 2010-11-12 23:03:40.643 2010-11-12 23:03:40.643 2010-11-12 23:03:40.840 2010-11-12 23:03:40.997 2010-11-12 23:03:45.910 2010-11-12 23:03:45.923 2010-11-10 23:11:11.087 2010-09-10 22:08:11.403 2010-11-07 23:11:06.170 2010-08-18 22:07:58.777 2010-11-12 23:03:45.930/Maekee

This is from my GroomingRunTime (Ran this now) 2010-11-12 23:03:40.643 2010-11-12 23:03:40.643 2010-11-12 23:03:40.840 2010-11-12 23:03:40.997 2010-11-12 23:03:45.910 2010-11-12 23:03:45.923 2010-11-10 23:11:11.087 2010-09-10 22:08:11.403 2010-11-07 23:11:06.170 2010-08-18 22:07:58.777 2010-11-12 23:03:45.930 /Maekee It seems it didn't run for at least two days. As Kevin Hollman says: Grooming of the OpsDB is called once per day at 12:00am What happens if you start the stored procedure p_PartitioningAndGrooming manually? Do you see any errors in you SQL Server logs regarding this stored procedure? Certifications: MCSA 2003|MCSE 2003|MCTS(4*)| MCTIP:SA

This is from my GroomingRunTime (Ran this now) 2010-11-12 23:03:40.643 2010-11-12 23:03:40.643 2010-11-12 23:03:40.840 2010-11-12 23:03:40.997 2010-11-12 23:03:45.910 2010-11-12 23:03:45.923 2010-11-10 23:11:11.087 2010-09-10 22:08:11.403 2010-11-07 23:11:06.170 2010-08-18 22:07:58.777 2010-11-12 23:03:45.930 /Maekee It seems it didn't run for at least two days. As Kevin Hollman says: Grooming of the OpsDB is called once per day at 12:00am What happens if you start the stored procedure p_PartitioningAndGrooming manually? Do you see any errors in you SQL Server logs regarding this stored procedure? Certifications: MCSA 2003|MCSE 2003|MCTS(4*)| MCTIP:SA

Back to my original post, why does the alert point to the old DBserver? If i execute p_PartitioningAndGrooming it successfully runs. Have not checked any logs for errors, how do i do that?/Maekee

Seems that the Alert has stopped arriving all of a sudden.. strange. But thanks for the replys/Maekee

I created a case for MS and found it to be a bug in OpsMgr. It was a Undiscover-problem. When we moved the RMS Role to a MS and then back, the MS still acted as a RMS for certain Rules. This was the resolution: Resolution: For the “Un-Discovery issue” we did the following: - We removed the old OpsMgr DB watcher object. To do this override the discovery for a group - that group being the Management Servers group. - Then ran remove-disabledmonitoringobject to remove the watcher objects. - Steps: • Open Operation Manager Shell. • Run the PowerShell Command: Remove-disabledmonitoringobject • Wait for few hours. The disabled discovered resources removed. - Then deleted the override so it will get re-discovered on the RMS again./Maekee