I did update to latest 2020.2 version and seems after this i started to get database maintenance is overdue. Table Name Oldest Entry Table NameOldest EntryOverdueAreaInterfaceErrors_CS_Detail7/14/2020 7:26:13 AM6 DaysInterfacesInterfaceTraffic_CS_Detail7/14/2020 7:26:13 AM6 DaysInterfaces I looked in the swdebugMaintenance log but there no errors (only success). Look int the forum but most of the post are old and talking about older versions and the solution is to do update to later version.

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Database maintenance is overdue after updating to latest version

I did update to latest 2020.2 version and seems after this i started to get database maintenance is overdue.

Table Name Oldest Entry

Table Name	Oldest Entry	Overdue	Area
InterfaceErrors_CS_Detail	7/14/2020 7:26:13 AM	6 Days	Interfaces
InterfaceTraffic_CS_Detail	7/14/2020 7:26:13 AM	6 Days	Interfaces

I looked in the swdebugMaintenance log but there no errors (only success).

Look int the forum but most of the post are old and talking about older versions and the solution is to do update to later version.

Find more posts tagged with

Accepted answers

All comments

pratikmehta003

Check the msmq folder once if it's not full... And try running the dB maintenance manually once and restart solarwinds services.

buzava

Thanks.

I check the size of the folder and there no problem .

Already tried restarting services and run manual maintenance .

There is no error in log and the maintenance job run successfully but i the overdue alert doesn't disappears.

dfairles

I'm having the same issue. Maintenance takes ab out 5 hours too.

Logs say they complete.

sv9780

Hello Team,

We have upgraded to 2020.2.1 yesterday and the DB maintenance is still running. its been about 6 hours.

Any help here to fix the DB maintenance long running issue.

shuth

You should check the maintenance log to see what it is stuck on or what is taking so long.

C:\ProgramData\SolarWinds\Logs\Orion\swdebugMaintenance.log

sv9780

I have reviewed the log and we see the Wireless tables taking almost 5+ hours.

bhermkens

I have the same thing, did you found a solution?

bharris1

@bhermkens Did you ever find a solution?

cory.chandler

Seeing similar problem with 2020.2.6 opened a case - Case#01057340 no luck so far. Below are the two things we are seeing...

Table Name Oldest Entry Overdue Area
InterfaceErrors_CS_Detail 3/5/2022 12:00:00 AM 9 Days Interfaces
InterfaceErrors_CS_Hourly 2/3/2022 12:00:00 AM 9 Days Interfaces
InterfaceErrors_CS_Daily 4/4/2021 12:00:00 AM 9 Days Interfaces
InterfaceTraffic_CS_Detail 3/5/2022 12:00:00 AM 9 Days Interfaces
InterfaceTraffic_CS_Hourly 2/3/2022 12:00:00 AM 9 Days Interfaces
InterfaceTraffic_CS_Daily 4/4/2021 12:00:00 AM 9 Days Interfaces

From deployment health...

ollowing errors were detected: - 2022-04-12 02:20:47 : Error in thread: System.Data.SqlClient.SqlException (0x80131904): dbm_ExecuteMaintenance: dbm_Move2Partitioned: ALTER TABLE SWITCH statement failed. There is no identical index in source table 'NPM_SAN.dbo.CPULoad_CS_stg' for the index 'IXBT_CPULoad_CS_Detail_hist_NodeID' in target table 'NPM_SAN.dbo.CPULoad_CS_Detail_hist' . ALTER TABLE CPULoad_CS_stg... - 2022-04-12 02:20:57 : Error in thread: System.Data.SqlClient.SqlException (0x80131904): dbm_ExecuteMaintenance: dbm_Move2Partitioned: ALTER TABLE SWITCH statement failed. There is no identical index in source table 'NPM_SAN.dbo.LoadAverage_CS_stg' for the index 'IXBT_LoadAverage_CS_Detail_hist_NodeID' in target table 'NPM_SAN.dbo.LoadAverage_CS_Detail_hist' . ALTER TABLE LoadAverage_CS_stg... - 2022-04-12 02:23:11 : Error in thread: System.Data.SqlClient.SqlException (0x80131904): dbm_ExecuteMaintenance: dbm_Move2Partitioned: ALTER TABLE SWITCH statement failed. There is no identical index in source table 'NPM_SAN.dbo.ResponseTime_CS_stg' for the index 'IXBT_ResponseTime_CS_Detail_hist_NodeID' in target table 'NPM_SAN.dbo.ResponseTime_CS_Detail_hist' . ALTER TABLE ResponseTime_CS_stg... - 2022-04-12 02:24:36 : Error in thread: System.Data.SqlClient.SqlException (0x80131904): dbm_ExecuteMaintenance: dbm_Move2Partitioned: ALTER TABLE SWITCH statement failed. There is no identical index in source table 'NPM_SAN.dbo.VolumeUsage_CS_stg' for the index 'IXBT_VolumeUsage_CS_Detail_hist_VolumeID_I4' in target table 'NPM_SAN.dbo.VolumeUsage_CS_Detail_hist' . ALTER TABLE VolumeUsage_CS_stg... - 2022-04-12 02:25:44 : Error in thread: System.Data.SqlClient.SqlException (0x80131904): dbm_ExecuteMaintenance: dbm_Move2Partitioned: ALTER TABLE SWITCH statement failed. There is no identical index in source table 'NPM_SAN.dbo.InterfaceErrors_CS_stg' for the index 'IXBT_InterfaceErrors_CS_Detail_hist_InterfaceID_NodeID_Timestamp_I4' in target table 'NPM_SAN.dbo.InterfaceErrors_CS_Detail_hist' . ALTER TABLE InterfaceErrors_CS_stg... - 2022-04-12 02:26:03 : Error in thread: System.Data.SqlClient.SqlException (0x80131904): dbm_ExecuteMaintenance: dbm_Move2Partitioned: ALTER TABLE SWITCH statement failed. There is no identical index in source table 'NPM_SAN.dbo.InterfaceTraffic_CS_stg' for the index 'IXBT_InterfaceTraffic_CS_Detail_hist_InterfaceID_Timestamp_I6' in target table 'NPM_SAN.dbo.InterfaceTraffic_CS_Detail_hist' . ALTER TABLE InterfaceTraffic_CS_stg...

What you can do

Please investigate these errors. Find out more on Knowledge Base.