White Papers

36 Dell Compellent Storage Center Management Pack 3.0 for Microsoft SCOM 2012/R2 Best Practices
When the SCOM SQL database reaches its maximum size, SCOM no longer accepts and displays new data.
In this case, error 10801 is displayed in the Operations Manager event log showing the following
information:
Discovery data couldn’t be inserted to the database. This could have happened because of one of the
following reasons:
 Discovery data is stale. The discovery data is generated by an MP recently deleted.
 Database connectivity problems or database running out of space.
 Discovery data received is not valid.
Could not allocate space for object in database ‘OperationsManager’ because the ‘PRIMARY’ filegroup is
full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional
files to the filegroup, or setting autogrowth on for the existing files in the filegroup.
If this error occurs, the database size needs to be increased, or autogrowth needs to be turned on. Please
refer to Microsoft TechNet for information on how to increase the size of a database.
For guidance with SQL Server database sizing for SCOM, please refer to the Operations Manager 2012
Sizing Helper Tool.
6.5.1 Using SCOM to monitor SQL server
Because SCOM and SQL are so closely tied together, monitoring of both servers is essential in maintaining
the health of the environment.
A SCOM monitoring agent can be installed on the SQL server used by SCOM. Keep in mind that the
monitoring agent will only report on the health of the operating system, and does not have any direct
hooks into SQL server.
Microsoft offers the System Center Management Pack for SQL Server which allows SCOM to monitor SQL
databases, jobs, counters, and more. The SQL server management pack can be downloaded from the
Microsoft Download Center.
6.6 Microsoft monitoring agent
Oftentimes, connection issues between the WMI Provider and SCOM servers can be resolved by simply
restarting the Microsoft monitoring agent on the WMI Provider server.
To restart the Microsoft monitoring agent:
1. Log on with administrator credentials to the Windows 2012/R2 server that is running the WMI
Provider.
2. Launch services by going to Start > Control Panel > Administrative Tools > Services.
3. Right-click on the Microsoft Monitoring Agent service and select Restart.
4. Verify the service restarted and is running.