Failed to execute 'Finalize Maintenance' During Database Maintenance

We recently updated to 2022.4.1, and have started to get Database Maintenance errors.

- 2023-02-20 03:15:02 : Retention interval settings not specified... - 2023-02-20 03:15:04 : Retention interval settings not specified... - 2023-02-20 03:15:07 : Retention interval settings not specified... - 2023-02-20 03:15:08 : Retention interval settings not specified... - 2023-02-20 03:21:18 : Failed to execute 'Finalize Maintenance [CustomPollerStatistics_CS]'... - 2023-02-20 03:21:26 : Failed to execute 'Finalize Maintenance [NPM_MulticastRoutingData_CS]'... - 2023-02-20 03:32:27 : [Failure] 1.88s Finalize Maintenance - NPM_MulticastRoutingData_CS... - 2023-02-20 03:32:27 : [Failure] 0.15s Finalize Maintenance - CustomPollerStatistics_CS...

I've seen that there are some known bugs with the Database Maintenance, but this seems more specific than that. I wasn't able to find anything in the KB articles, and didn't see anything that specifically mentioned the Finalize Maintenance. Any help would be appreciated.

Find more posts tagged with

database_maintenance

Accepted answers

All comments

lukedoub

We are getting some of the same errors running 2022.4.0. I'm planning on upgrading to 2023.1 GA having been told these are fixed in it. SW just released an article within last two weeks (somewhat) detailing this bug, linking at bottom.

What are the effects y'all are seeing? Our tempdb and log DB have been growing ad nauseam, which requires a maintenance and downtime every 2 or 3 weeks to fix.

support.solarwinds.com/.../Database-Maintenance-Failed-Failed-to-execute-Finalize-Maintenance-CustomPollerStatistics-CS

P_Craddock

You might want to hold off on that upgrade. I went to 2023.1.0 and it has created database errors during the nightly process. There is a case open on it, and as of yet no fix. Not to mention all the other bugs that have turned up. I would stay at the release you are at for now.

lukedoub

Did you upgrade to the Release Candidate or the GA release? The GA had a fix specifically for the "Failure to Finalize Maintenance" bug that was not included in the Release Candidate. Just wondering because if you're on RC I'll maintain a little bit of hope that 2023.1 GA could fix my problem, but if you're on GA then I doubt it.

P_Craddock

I am on GA.

lukedoub

Sharing this in case it applies to you. From another thread about the DBM error, the supposed root cause and why you still may experience it in 2023.1:

We implemented a fix in 2023.1 which explicitly prioritizes database maintenance over incoming data, but it needs a support from SQL server. This support was added in SQL 2016 SP1 CU3, however, it is turned off by default. That's why trace flag 1237 has to be turned on manually. SQL versions 2017 and newer have this feature turned on by default. More details in https://support.microsoft.com/kb/4025261

thread:

thwack.solarwinds.com/.../database-maintenance-error

Christopher.King

Awesome, I'll definitely need to check this out.