Database Maintenance Failure

Having issues with the database maintenance not working and throwing errors when it runs.  The issue is that it fails when updating the "VolumeUsage" and deleting old files.  

Errors Below:

SolarWinds.Data.DatabaseMaintenance.Reporter -    [Failure] 0.01s Remove temporary system files - Files

SolarWinds.Data.DatabaseMaintenance.Reporter - [Failure] 2.35s Compute baseline statistics - VolumeUsage

Been working with Support over a month and no one can resolve this issue.  Our database is in a cluster so, can't make changes without effecting the entire cluster/  Anyone has any ideas on these issues?  My brain hurts now.  

  • What version are you running?  You don't mention that in the post.

  • Sorry.. We are running 202.4.2.  Also, I forgot to said that our Database is in a SQL cluster.. this is the only instance having issues.  

  • Your version number got truncated.  Are you running 2023.4.2?

  • I think I remember this being an issue with this particular release.  Is there a reason you haven't updated to 2024.1?  That's what I'm running and I just checked the DB Maintenance logs and those issues you report aren't in the logs anywhere.

  • Thanks... I'll try that this weekend.  Been working with support on this issue for sometime now and it's frustrating. 

  • Hello and GM KMSigma. I have a support case open (01592717) on a similar issue. We are running 2024.1 and seeing this in the logs.                                  "Database maintenance started on Thursday, March 28, 2024 has finished with errors."                                                                                                       2024-03-28 02:19:05,301 [1] WARN SolarWinds.Data.DatabaseMaintenance.OrionNotificationHelper - Detected that operation [Summarize detailed data]-[InterfaceAvailability] failed 3 times in a row.
    2024-03-28 02:19:05,301 [1] WARN SolarWinds.Data.DatabaseMaintenance.OrionNotificationHelper - Detected that operation [Summarize hourly data]-[InterfaceAvailability] failed 3 times in a row.

  • I just upgraded to 2024.1 and so far no errors with the database.  Here's what support sent to me to try:


    Note: Please save a backup of your Orion Database and a snapshot of the Orion server.

    Possible Deduplication, The node involved had multiple sysname added based on the database values

    Next Step:

    Turn off the SysName deduplication mechanism

    How to turn off the SysName de-duplication mechanism:

    Part A

    In c:\Program Files (x86)\SolarWinds\Orion\SolarWinds.Orion.Discovery.Job.dll.config there are 3 keys:
    So just change the DisableSysNameDuplicateDetector value to True and save the file. Restart Orions Services to take effect.

    <add key="DisableMacDuplicateDetector" value="false" />
    <add key="DisableSysNameDuplicateDetector" value="true" />
    <add key="DisableDNSDuplicateDetector" value="false" />

    Part B

    In the database, the Settings table there are following settings:

    Discovery-Import-DNSDeDuplicator-Weight (default CurrentValue=27)
    Discovery-Import-MacDuplicateDetector-Weight (default CurrentValue=26)
    Discovery-Import-SysNameDeDuplicator-Weight  (default CurrentValue=25)                     

    To disable, one needs to change the Discovery-Import-SysNameDeDuplicator-Weight

    - CurrentValue= 0 directly from SQL Management studio in edit mode or by executing following statement:

    UPDATE Settings SET CurrentValue = 0 WHERE SettingID = 'Discovery-Import-SysNameDeDuplicator-Weight             
    Where applicable, can also use the following:

    update [dbo].[Settings] set CurrentValue = 0 where settingid = 'Discovery-Import-DNSDeDuplicator-Weight'
    update [dbo].[Settings] set CurrentValue = 0 where settingid = 'Discovery-Import-MacDuplicateDetector-Weight'

    The Sysname deduplicator should be bypassed by these steps.

  • Thanks Clark1812! I sent support this link to see if similar to my DB maintenance error. I'll post back later.

  • Hello Clark1812. Thanks for the information. Just wanted to let you know I am working with SW's support on this. This is their response. I'll update things here after we fix the problem. Hi Rick,

    Upon checking the Thwack post I don't recommend to try the same thing as the node values may defer. Let me pull additional resources on this for further analysis and recommendations.

    Thanks in advance.

    Technical Support