December 21, 2009 at 7:19 am
I have a database that I have a weekly maintenance plan set up to run. The first thing it does is do a DBCHECK. This last week I started getting the following error:
Description: Executing the query "DBCC CHECKDB(N'XXXXXXX') WITH NO_INFOMSGS " failed with the following error: "Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. End Error
I have done some research and it appears that I may have a corrupt database, but the "Problems with the query" part is throwing me off.
Any help is appreciated.
December 21, 2009 at 7:21 am
Please run the following from management studio and post the full output.
DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
I do hope you have a clean backup of that database. Also, take a look at this article. http://www.sqlservercentral.com/articles/65804/
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
December 21, 2009 at 7:43 am
Ok. Below is the log that I got from running the command that you requested. There doesn't appear to be a problem now, but nothing has been done to the DB.
Date12/21/2009 8:38:18 AM
LogSQL Server (Current - 12/21/2009 8:38:00 AM)
Sourcespid53
Message
DBCC CHECKDB (XXXXXXXXX) WITH all_errormsgs, no_infomsgs executed by XXXXXXX found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 5 seconds. Internal database snapshot has split point LSN = 00001949:0000d996:0001 and first LSN = 00001949:0000d995:0001. This is an informational message only. No user action is required.
December 21, 2009 at 7:58 am
Ok, good.
I have seen this before, can't necessarily tell you exactly what causes it though. Sometimes things like an index rebuild will 'fix' corruption. It could also have been that tempDB really was full.
Check the windows event logs, make sure there are no other errors there and keep an eye on this. Also might be worth doing some diagnostics on the IO subsystem, make sure everything's as it should be.
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
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply