The best resource to use is sp_resetstatus against the "suspect" database.

I encountered this problem earlier and sp_resetstatus was able to solve that.

Sekhar