Somewhere along the way, a database in a distributed availability group must not have been removed cleanly and now it cannot be removed from the secondary's to rejoin AG. When i run alter database db1 set hadr off, it says database doesn't exist.
current state:
AG1
DB1 online & active on primary, not part of any AG
DB1 not present on secondary
AG2
DB1 not present on Primary but in availability group it says not joined/not healthy
DB1 not present on Secondary but in availability group it says not joined/not healthy
How can i force remove the database on AG2? Once i remove it there, i think i'll be able to re-establish and get it synchronized.
- This topic was modified 3 years, 7 months ago by mwoolery.