Partitioning and grooming has completed recently Monitor

  • ID:  Microsoft.SystemCenter.OpsMgrDB.PartitioningAndGroomingMonitor
  • Description:  This monitor detects if partitioning and grooming processes have not completed successfully for too many days in a row.
  • Target:  Operations Manager Operational Database Watcher
  • Enabled:  Yes

Operational States

Name State Description
Partitioning and grooming has completed recently Success  
Partitioning and grooming has not completed recently Warning  

Overridable Parameters

Parameter Name Default Value Description Override
Interval (seconds) 86400 This workflow runs a script on a recurring schedule. The interval is the number of seconds that the workflow should wait from one run to the next. Change this value if you want the workflow to run more or less frequently.
Sync time 12:01  
Timeout (seconds) 300 This workflow runs on script on a recurring schedule. The timeout is the number of seconds that the script is allowed to run before it will be forced to stop. Note: the timeout should always be less than the interval to ensure that multiple instances of the script do not run at the same time.
Maximum days since last success 2 This workflow uses the "maximum days since last success" value as a threshold to determine state. Set this to the maximum number of days that can pass without partitioning and grooming completing successfully, before it is considered a problem.
Sample Count before alerting 2 Sample count to wait until change the monitor to the warning state.

Alert Details

Monitor State Message Priority Severity Auto Resolution
Partitioning and grooming has not completed recently (Warning) Partitioning and grooming has not completed recently High Critical Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

The processes that run to partition and groom the data stored in the operational database have not completed successfully in recent history. If these processes continue to not complete successfully then the performance of the operational database will be negatively impacted, which will slow down the entire management group. Ultimately the operational database will fill up entirely and the management group will cease to function.

Causes

The reason this alert has been generated is because the partitioning and grooming process have not completed successfully within recent history. By default, this monitor is configured to generate an alert if the processes have not completed successfully within the previous 2 days. Some of the causes for the partitioning and grooming process not completing successfully include the following:

  • The "Partitioning and Grooming" rule is disabled

  • The "Partitioning and Grooming" rule is failing to access the SQL Server hosting the operational database in order to run the SQL stored procedures that perform grooming and partitioning.

  • The SQL stored procedures that perform partitioning and grooming are failing due to insufficient SQL log file space for the operational database.

Resolutions

The following steps cover how to troubleshoot and resolve this issue for the most common issues:

  • Ensure the "Partitioning and Grooming" rule does not have any overrides applied to it which would disable it.

  • The "Partitioning and Grooming" rule is run on the collection management server and runs under the credentials provided in the "Operational Database Account" Run As profile. If no credentials are provided in the "Operational Database Account" Run As profile, then the collection management server's default action account will be used. Confirm that the account being used to run the rule is configured with sufficient permissions. Refer to the help topic "How to Create a New Run As Account for Accessing the Operations Manager Database" (http://go.microsoft.com/fwlink/?LinkID=824999) for more information.

  • The process of partitioning and grooming the operational database requires space in the SQL transaction log of the operational database. If there is not sufficient space in the transaction logs, then partitioning or grooming can fail. You can review the percent of space available in the transaction log with the "SQLServer:Databases\Percent Log Used" performance counter. Add more space to existing transaction log file(s), add more files or take the necessary steps to free up space within the existing log file(s) so that partitioning and grooming has enough space to complete. This is especially important if log shipping has been enabled on the operational database. Refer to the "Understanding and Managing Transaction Logs" (http://go.microsoft.com/fwlink/?LinkId=193419) topic in the SQL books online for more information about transaction logs.

External References
This monitor does not contain any external references.

See Also for System Center 2016 Operations Manager inbox MP hotfix for WMI health monitor issue Management Pack


Downloads for System Center 2016 Operations Manager inbox MP hotfix for WMI health monitor issue Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED