Well,

I am not planning (and certainly, will not) to change a database that is not in suspect state and fully operational to "emergency mode" just to check.

What I will do(only because it is up and running and does not look is generating logical problems with the query) is restore a fresh backup on a different server and run DBCC command again; I'll do that manually and via Maintenance Plan or job.

I got the feeling is a permissions or job problem and not a logical or physical error on the database. Hopefully, that will be the case.