Thanks for the replies.

We now had these kind of issues reported twice with 2 different databases and we found out that one of guys have changed the db_owner permissions from a security standpoint. But some of those were required by application teams to be as is. Before we start getting more and more calls about remaining db's, we thought we would find what how it was before so that we can answer them accordingly or rather fix them the way they were originally.

I am still trying the solution given and cross verify with database permissions and roles.

THanks,