Turns out that the database wasn't properly upgraded from 8.1.6 .. in the first place and no one checks the database so I was the lucky one who did because of the patch install

The appropriate scripts have been run and the error is gone