Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

checkdb - error but no issue? Expand / Collapse
Author
Message
Posted Friday, March 14, 2014 7:05 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, October 3, 2014 8:03 AM
Points: 6, Visits: 49
Hello all and thanks for your time.
I just added th Check Database Integrity Task to my daily maintenance plan yesterday, and this morning I got an alert from SQL:

Microsoft(R) Server Maintenance Utility (Unicode) Version 10.0.5512 Report was generated on "myServer\myInstance".
Maintenance Plan: 7 Day Retention Full Backups
Duration: 00:01:55
Status: Warning: One or more tasks failed.
Details:
Check Database Integrity Task (myServer\myInstance) Check Database integrity on Local server connection Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All databases
Include indexes
Task start: 2014-03-14T01:00:01.
Task end: 2014-03-14T01:00:11.
Failed: (-1073548784) Executing the query "DBCC CHECKDB(N'myDatabase') 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.

If i run the tsql manually, with no_infomsgs, i get:
Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.

I checked TempDB, 35.13MB size with 30.98MB available, seems ok.
When I viewed the msdb.suspect_pages table, I found an entry:
database_id file_id page_id event_type error_count last_update_date
8 1 458 2 7 2014-03-14 08:54:56.457

I would have just restored from backup, but since I just added this task to the maint plan, I fear it's been going on for awhile. I don't see any issues in production, just this message.

I'm wondering A. is something wrong? B. What is wrong? C. Can I fix it without a backup?

Thanks again for your input.

Jason
Post #1551139
Posted Friday, March 14, 2014 7:52 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 10:25 AM
Points: 40,385, Visits: 36,827
Corrupt page in a system table. This is not good news. There may well be more corruption, we just don't know.

Can you restore your latest backup somewhere else and run checkDB on that?



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1551164
Posted Friday, March 14, 2014 8:06 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, October 3, 2014 8:03 AM
Points: 6, Visits: 49
As you probably feared, my oldest backup has been restored and still gives me the same errors.

I am guessing it is a matter of time before the application (Citrix provisioning server) accesses the bad page and freaks out, but will the problem get worse?

I also guess that I should start rebuilding the database in the mean time.

Any further advice?

Thanks Gail!
Post #1551169
Posted Friday, March 14, 2014 8:23 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Yesterday @ 5:49 AM
Points: 826, Visits: 345
Check with "DBCC DBINFO WITH tableresults". The field dbi_dbcclastknowngood will show you the last time dbcc succeded without any errors in the DB. This will help you to identify the good backup as well if you want to restore.
Post #1551173
Posted Friday, March 14, 2014 8:45 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, October 3, 2014 8:03 AM
Points: 6, Visits: 49
Good tip. Too bad it came up with 1900-01-01, heh. If anyone else read this who doesn't run any sort of db corruption detection, learn from my mistake
Post #1551180
Posted Friday, March 14, 2014 8:52 AM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Wednesday, November 19, 2014 7:09 PM
Points: 593, Visits: 931
Looks like you need to create a new database and start moving data.



Microsoft Certified Master - SQL Server 2008
Follow me on twitter: @keith_tate

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1551184
Posted Friday, March 14, 2014 9:03 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Yesterday @ 5:49 AM
Points: 826, Visits: 345
Is the result that mentioned came up for your user Db or for system DB's. You have to execute it in all the DB's.
Post #1551190
Posted Friday, March 14, 2014 11:13 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, October 3, 2014 8:03 AM
Points: 6, Visits: 49
I only ran it against the db that is in question. Now, the error says system tables, but you are saying the problem could be in system dbs? if so, why did the dbcc checkdb not find issue with them? Genuinely curious.

Anyways, I haven't even run dbcc checkdb against any dbs in this instance since it's inception.
Post #1551258
Posted Friday, March 14, 2014 11:37 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Yesterday @ 5:49 AM
Points: 826, Visits: 345
I haven't told the error is with system DB. Even if you have dbcc scheduled on weekly basis, model DB at times shows the good time as the date that you mentioned. That was why I have asked you whether you have executed it on User or System DB. Since the result was for User DB itself, try executing dbcc with allow data loss(with SQL Server anything can happen) or as Gail mentioned restore the DB.
Post #1551271
Posted Friday, March 14, 2014 12:53 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 10:25 AM
Points: 40,385, Visits: 36,827
Bijoy.Kaiprath (3/14/2014)
try executing dbcc with allow data loss


NO! NO! NO! (not that it will do a damned thing in this case)



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1551308
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse