CU31 breaking non clustered Availability Groups

Question

Post reply

CU31 breaking non clustered Availability Groups

bmcmeans76

SSC Enthusiast

Points: 176
More actions
February 20, 2025 at 1:18 pm

#4542090

Last week I downloaded and applied the newest CU31 patch to our lower environment SQL 2019 servers. Most took it just fine however, I've discovered a bug in which if a system has an Availability Group established but is not part of a cluster, it makes any database involved in said AG unavailable. Even in the dashboard, it shows the primary instance offline, but clearly it is not. Installed on a system with a cluster and it works fine.
I did also try applying to both servers in the AG and fully rebooting for good measure, but still did not work.
I saw in the KB article that one of the fixes included is in regards to creating an AG when the name is longer than 64 characters, but that's all. Has anyone else encountered this? Plan to submit to Microsoft as well, but when I started the process it made it seem like I had to have paid support?

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Site Owners SSC Guru Points: 80356 More actions · Answer 1

Thanks for posting your issue and hopefully someone will answer soon.

This is an automated bump to increase visibility of your question.

Razvan Socol SSCarpal Tunnel Points: 4962 More actions · Answer 2

Yes, we also experienced this problem when installing CU 31 for SQL 2019.

We have a Basic Availability Group (on two SQL Server Standard Edition) and after we installed the updates on the primary server we found in the log "Always On: AG integrity check failed to find AG name to ID map entry with matching group ID for AG [...]", then "Always On: The local replica of availability group [...] is being removed." and the databases remained as Restoring.

After performing an "RESTORE DATABASE [...] WITH RECOVERY", everything was ok.

This reply was modified 6 months, 2 weeks ago by Razvan Socol.

bmcmeans76 SSC Enthusiast Points: 176 More actions · Answer 3

Thanks for responding. Unfortunately in my scenario, the databases don't say (Restoring...). At first blush they look available but when you try to expand it, it says data base is unavailable.

I attempted to submit to Microsoft, but through all of the options it seems like the only way to do so is if you have a paid support agreement.

bmcmeans76 SSC Enthusiast Points: 176 More actions · Answer 4

Disregard, I saw on the KB page for the patch tonight they updated it and this is now a known bug for AG's with a cluster type of NONE or EXTERNAL. If you want the patch installed, need to recreate the AG.