Answered SCOM 2007 Database CPU running 100%

  • Thursday, June 28, 2012 8:11 PM
     
     

    SQL 2008 version 10.0.4000.0 on Win2008R2. Four CPUs, all at 100% and 12gb ram memory and using almost all of it.
    After a reboot, it goes right back to 100%.  No errors when I ran a checkdb.

    My DBA gave me this report of the operations taking up the CPU

    Database . task execution count Total CPU time Average CPU
    OperationsManagerDW dbo StateChangeEventList 7 171871040 24.55300571
    OperationsManager dbo p_InstallMonitors 1 19941398 19.941398
    OperationsManager dbo p_InstallTypesAndReltypes 1 16009750 16.00975
    OperationsManagerDW Exchange2010 AvailabilityAggregate 33 234413048 7.103425697
    OperationsManagerDW dbo StateAggregate 3 12486326 4.162108667
    OperationsManager dbo p_ManagementPackRemove 5 20672843 4.1345686
    OperationsManagerDW Exchange2010 AggregateNumbers 3 10140622 3.380207333
    OperationsManagerDW dbo ManagedEntityTypeImageRebuild 4 9571291 2.39282275
    OperationsManager dbo p_MPImportXML 4 6333939 1.58348475
    OperationsManager dbo p_ManagementPackFinishInstall 4 3292955 0.82323875
    OperationsManager dbo p_GetCounter 28068 21802697397 0.776781295
    OperationsManager dbo fn_FindMonitorParameterId 1 517577 0.517577

    I saw this issue, but I'm running an earlier version of SQL so it may not be applicable.
    http://blogs.technet.com/b/operationsmgr/archive/2011/02/03/fix-sql-server-hits-100-cpu-utilization-when-there-are-configuration-update-requests-in-scom-2007.aspx

    Any suggestions?


    • Edited by c_kubie Thursday, June 28, 2012 8:56 PM
    •  

All Replies

  • Friday, June 29, 2012 8:59 AM
    Moderator
     
     

    Hi,

    For this issue, maybe you can refer to the following similar article:

    Operations Manager Data Warehouse High CPU Utilization

    http://www.afinn.net/2008/10/29/operations-manager-data-warehouse-high-cpu-utilization/

    Also, you may install the latest cumulative update to see the result.


    Alex Zhao

    TechNet Community Support

  • Friday, June 29, 2012 1:37 PM
     
     Answered

    This many not be the direct solution, but I changed the grooming / data retention to 14 days and it now performing at 40%.  I may have purged out anything that was causing the high CPU.

    Alex,
    I'll post back on the rebuilding indexes you suggest in the link.  I'm waiting till I get a solid backup before I try something else.

  • Thursday, July 05, 2012 3:55 AM
    Moderator
     
     

    Hi,

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as "Answered" as the previous steps should be helpful for many similar scenarios.

    In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.

    Thanks,


    Yog Li

    TechNet Community Support