I'll have to check up on that. This happened on a db that I am not administering. This was reported by another DBA on site.