Hi Colin,
I’ve spoken to my team members about it, but no one has made any modifications to the SonarQube database.
In this post it seems like the same thing has happened but with a different index and column.
It’s a strange one, because if no one has made any manual changes then how do those columns get generated?
What I managed to do was go from 9.9.4 directly to 10.1.0 without making any changes to the db, besides running the /setup. That error only came in once attempting to upgrade to 10.4.1. Is it possible that it may have happened somewhere during the first upgrade perhaps?