Forum Discussion

TJensen's avatar
TJensen
Level 4
7 years ago

Old Fragmentation Warnings/Event 41561

I'm getting old fragmentation warnings every day. "Index fragmentation was detected after scan at '2/11/2018 1:00 PM'. Disregard this warning if you have defragmented the listed indexes since." I'v...
  • Marcde's avatar
    Marcde
    7 years ago

    You could run the computefragmentation stored procedure which will update the relevant entries based on the fragmentationstatus on the time of execution. Last time I verified this was under 11.0.1 but might work as well on EV 12. The best is to execute as the last part of the maintenance or shortly after the maintenance.

     

    Running the 'ComputeFragmentation' stored procedure

    https://www.veritas.com/support/en_US/article.000023310

     

    Regards

    Marc

GertjanA's avatar
GertjanA
Moderator

Hello T.

You'll have to delete the row.

Delete from MonitoringHistory
where MonitoringItemEntryId = 'ID_from_monitoring_table'

Be advised that the 'where' clause has to have a unique row identifier. I'm not sure monitoringitementryid is unique, but as you are able to determine which row it is, you can find it yourself I assume.

Marcde's avatar
Marcde
Moderator
7 years ago

You could run the computefragmentation stored procedure which will update the relevant entries based on the fragmentationstatus on the time of execution. Last time I verified this was under 11.0.1 but might work as well on EV 12. The best is to execute as the last part of the maintenance or shortly after the maintenance.

 

Running the 'ComputeFragmentation' stored procedure

https://www.veritas.com/support/en_US/article.000023310

 

Regards

Marc

  • TJensen's avatar
    TJensen
    Level 4
    7 years ago

    What seems to have resolved this was manually running an index re-org (its in my nightly maint plan anyways) and then running the stored procedure to compute fragmentation.