November 11, 2015 at 10:32 am
Hi,
We recently had an issue with our SQL Server 2012 maintenance routines when our VMware software went rogue and caused our log file drives to fill up. This was unfortunately rectified by VMware by deleting who knows what as I wasn't here at the time. Since then my maintenance job that rebuilds index on my numerous databases keeps coming back with errors. I have read that this seems to be a common issue once VMware have done their magic, it may have nothing to do with them at all and all be coincidence but could someone help me with what the issue is below and how I can fix it please.
Thanks Phil
Check Catalog Msg 3851, State 1: An invalid row (class=60,depid=2,depsubid=0) was found in the system table sys.syssingleobjrefs (class=60). Check Catalog Msg 3851, State 1: An invalid row (class=60,depid=3,depsubid=0) was found in the system table sys.syssingleobjrefs (class=60). Check Catalog Msg 3851, State 1: An invalid row (class=60,depid=4,depsubid=0) was found in the system table sys.syssingleobjrefs (class=60). Check Catalog Msg 3851, State 1: An invalid row (class=60,depid=5,depsubid=0) was found in the system table sys.syssingleobjrefs (class=60).
And so on......
November 12, 2015 at 3:41 am
I have now managed to work out which database was causing the ReIndex Issue in my Maintenance plan and have been able to remove it.
Thanks Phil
November 12, 2015 at 5:15 am
Have you fixed the corruption in the DB, or did you just stop reindexing that database?
And what the hell does VMWare do that causes database corruption?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 12, 2015 at 6:06 am
Hi,
In relation to the VMWare statement all I know is that they asked the IT Manager to remove some entries from the master database what these were I do not know yet and am awaiting a transcript of the call, from what I can tell and having run various checks on the master DB everything is working as it should be, I am going to run a compare with one of our backups's to see if I can establish what was deleted.
The fix for the database issues is not to reindex that database, it was a temp restore that I have now been able to drop. Strange though, under the maintenance item where I had originally select to reindex all the necessary databases this restored database never showed which threw me of a little bit, now that I have removed it everything is back to working fine.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply