March 9, 2010 at 6:59 am
Output from the following command:
DBCC CheckDB ('Database_Name') WITH NO_INFOMSGS, ALL_ERRORMSGS
Msg 8928, Level 16, State 1, Line 1
Object ID 261575970, index ID 1, partition ID 72057598963482624, alloc unit ID 72057594043826176 (type LOB data): Page (1:713625) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 261575970, index ID 1, partition ID 72057598963482624, alloc unit ID 72057594043826176 (type LOB data), page (1:713625). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 230819849 and -4.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 261575970, index ID 1, partition ID 72057598963482624, alloc unit ID 72057594043826176 (type LOB data). The off-row data node at page (1:713625), slot 0, text ID 85432795136 is referenced by page (1:74024), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 261575970, index ID 1, partition ID 72057598963482624, alloc unit ID 72057594043826176 (type LOB data): Page (1:713626) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 261575970, index ID 1, partition ID 72057598963482624, alloc unit ID 72057594043826176 (type LOB data), page (1:713626). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 230819849 and -4.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 261575970, index ID 1, partition ID 72057598963482624, alloc unit ID 72057594043826176 (type LOB data). The off-row data node at page (1:713626), slot 0, text ID 85432795136 is referenced by page (1:74024), slot 0, but was not seen in the scan.
Msg 8928, Level 16, State 1, Line 1
Object ID 261575970, index ID 1, partition ID 72057598963482624, alloc unit ID 72057594043826176 (type LOB data): Page (1:713627) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 261575970, index ID 1, partition ID 72057598963482624, alloc unit ID 72057594043826176 (type LOB data), page (1:713627). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 230819849 and -4.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 261575970, index ID 1, partition ID 72057598963482624, alloc unit ID 72057594043826176 (type LOB data). The off-row data node at page (1:713627), slot 0, text ID 85432795136 is referenced by page (1:74024), slot 0, but was not seen in the scan.
Msg 8929, Level 16, State 1, Line 1
Object ID 261575970, index ID 1, partition ID 72057598963482624, alloc unit ID 72057599089508352 (type In-row data): Errors found in off-row data with ID 85432795136 owned by data record identified by RID = (1:1368905:38)
CHECKDB found 0 allocation errors and 10 consistency errors in table 'AllDocStreams' (object ID 261575970).
CHECKDB found 0 allocation errors and 10 consistency errors in database 'Database_Name'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Database_Name).
Unfortunately, I don't have this level of SQL DBA experience and I'm looking for a little guidance. I've read through the threads and it looks as though we've got a couple of options. Unfortunately, I restore of this database will most likely yield the same consistency errors. My colleague and I have recently inherited this implementation of Sharepoint and we are recovering from a hardware error. We are wondering if the best course of action is to just backup the database and run: DBCC CheckDB 'database_name', repair_allow_data_loss????
March 9, 2010 at 7:05 am
Restore from backup if you can.
A repair might cause problems with sharepoint because of the way it discards data. Not sure here, I have asked an expert on corruption and sharepoint for a 2nd opinion.
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
March 9, 2010 at 8:48 am
Keep me posted, I'm definitely interested in the response.
March 9, 2010 at 10:23 am
SharePoint's tricky, because allowing CHECKDB to delete some rows in the AllDocStreams table could mean you lose documents, potentially 'corrupting' the search database too and causing SharePoint failures.
You've got one damaged row in that table, so you're going to lose one document.
If you can restore from a backup, and the downtime while doing that is palatable, go for that route. If not, run the repair.
One thing I'd do is have a look at the row that's damaged:
dbcc traceon (3604)
go
dbcc page (yourdbname, 1,11368905,3)
go
And look for slot 38 - you should see the name of the doc. To be honest, in this case you may be better running the repair, for simplicity.
You also need to checkout your I/O subsystem - as it looks like that's what caused the problem. The damaged pages are contiguous, which screams "I/O subsystem" at me.
Cheers
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
March 9, 2010 at 10:33 am
Why did this happen? Was there a power failure?
As last resort you might consider truncating the table or you can run a DBCC CHECKDB statement with the REPAIR_ALLOW_DATA_LOSS option to delete the damaged rows. Then, you can reload the table from the original data source.
Note: Don't forget to backup database before you perform this operation.
March 10, 2010 at 10:23 am
I'll probably end up running DBCC checkDB restore_rebuild first to see what happens but I'll have to wait until the weekend to put the DB in single user mode. Stay Tuned.
March 10, 2010 at 10:32 am
It won't do anything to help you. The reason why I got it to say what the minimum repair level is, is because that's what you'll need to run for it to fix the problems. You'll be wasting time running repair_rebuild. These corruptions need to delete a record in the table, hence it says you need to run with repair_allow_data_loss.
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
March 10, 2010 at 12:35 pm
Understood, I'll forgo the repair_rebuild and just do the repair_allow_data_loss. Thanks for the heads up.
March 11, 2010 at 1:05 am
No good backup then?
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
March 11, 2010 at 6:46 am
We have regular backups but we aren't sure for how long this problem existed as this is an inherited problem. The powers that be are okay with losing one document to resume the normal/successful maintenance plan of this database. Worse case, is we revert back to a backup if something crops up.
March 11, 2010 at 8:42 am
May I suggest, going forward, that you institute regular database integrity checks. Regular enough that, should there be a problem, restoring from backup is always an option.
Also keep in mind what Paul said about possible effects on the search database and sharepoint as a whole.
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
March 11, 2010 at 10:04 am
We've setup our maintenance plans to check the integrity of the databases every night. Plus we've got SCOM in place to alert us of any future failed backups and other related SQL issues.
March 11, 2010 at 12:21 pm
Thats good, Don't always depend on SCOM alerts set up SQL alerts also.
March 15, 2010 at 6:18 am
Two things, first the short part; We've also got SQL alerts setup in addition to SCOM alerts in case anything on our SQL cluster goes strange. Second, running the dbcc checkdb ('database name', repair_allow_data_loss) command seems to have done the trick. I did complete backups of all Sharepoint databases before executing the command and the maintenance plan is now succeeded normally. Here's the output of the command results for anyone interested:
DBCC results for 'database_name'.
Service Broker Msg 9675, State 1: Message Types analyzed: 14.
Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.
Service Broker Msg 9667, State 1: Services analyzed: 3.
Service Broker Msg 9668, State 1: Service Queues analyzed: 3.
Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.
Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.
Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.
Service Broker Msg 9605, State 1: Conversation Priorities analyzed: 0.
DBCC results for 'sys.sysrscols'.
There are 2921 rows in 29 pages for object "sys.sysrscols".
DBCC results for 'sys.sysrowsets'.
There are 328 rows in 7 pages for object "sys.sysrowsets".
DBCC results for 'sys.sysallocunits'.
There are 374 rows in 11 pages for object "sys.sysallocunits".
DBCC results for 'sys.sysfiles1'.
There are 2 rows in 1 pages for object "sys.sysfiles1".
DBCC results for 'sys.syspriorities'.
There are 0 rows in 0 pages for object "sys.syspriorities".
DBCC results for 'sys.sysfgfrag'.
There are 2 rows in 1 pages for object "sys.sysfgfrag".
DBCC results for 'sys.sysphfg'.
There are 1 rows in 1 pages for object "sys.sysphfg".
DBCC results for 'sys.sysprufiles'.
There are 2 rows in 1 pages for object "sys.sysprufiles".
DBCC results for 'sys.sysftinds'.
There are 0 rows in 0 pages for object "sys.sysftinds".
DBCC results for 'sys.sysowners'.
There are 16 rows in 1 pages for object "sys.sysowners".
DBCC results for 'sys.sysprivs'.
There are 135 rows in 1 pages for object "sys.sysprivs".
DBCC results for 'sys.sysschobjs'.
There are 1096 rows in 21 pages for object "sys.sysschobjs".
DBCC results for 'sys.syscolpars'.
There are 8387 rows in 141 pages for object "sys.syscolpars".
DBCC results for 'sys.sysnsobjs'.
There are 1 rows in 1 pages for object "sys.sysnsobjs".
DBCC results for 'sys.syscerts'.
There are 0 rows in 0 pages for object "sys.syscerts".
DBCC results for 'sys.sysxprops'.
There are 0 rows in 0 pages for object "sys.sysxprops".
DBCC results for 'sys.sysscalartypes'.
There are 37 rows in 1 pages for object "sys.sysscalartypes".
DBCC results for 'sys.systypedsubobjs'.
There are 0 rows in 0 pages for object "sys.systypedsubobjs".
DBCC results for 'sys.sysidxstats'.
There are 1075 rows in 21 pages for object "sys.sysidxstats".
DBCC results for 'sys.sysiscols'.
There are 1825 rows in 13 pages for object "sys.sysiscols".
DBCC results for 'sys.sysbinobjs'.
There are 23 rows in 1 pages for object "sys.sysbinobjs".
DBCC results for 'sys.sysaudacts'.
There are 0 rows in 0 pages for object "sys.sysaudacts".
DBCC results for 'sys.sysobjvalues'.
There are 2011 rows in 653 pages for object "sys.sysobjvalues".
DBCC results for 'sys.sysclsobjs'.
There are 16 rows in 1 pages for object "sys.sysclsobjs".
DBCC results for 'sys.sysrowsetrefs'.
There are 0 rows in 0 pages for object "sys.sysrowsetrefs".
DBCC results for 'sys.sysremsvcbinds'.
There are 0 rows in 0 pages for object "sys.sysremsvcbinds".
DBCC results for 'sys.sysxmitqueue'.
There are 0 rows in 0 pages for object "sys.sysxmitqueue".
DBCC results for 'sys.sysrts'.
There are 1 rows in 1 pages for object "sys.sysrts".
DBCC results for 'sys.sysconvgroup'.
There are 0 rows in 0 pages for object "sys.sysconvgroup".
DBCC results for 'sys.sysdesend'.
There are 0 rows in 0 pages for object "sys.sysdesend".
DBCC results for 'sys.sysdercv'.
There are 0 rows in 0 pages for object "sys.sysdercv".
DBCC results for 'sys.syssingleobjrefs'.
There are 146 rows in 1 pages for object "sys.syssingleobjrefs".
DBCC results for 'sys.sysmultiobjrefs'.
There are 16651 rows in 118 pages for object "sys.sysmultiobjrefs".
DBCC results for 'sys.sysguidrefs'.
There are 0 rows in 0 pages for object "sys.sysguidrefs".
DBCC results for 'sys.syscompfragments'.
There are 0 rows in 0 pages for object "sys.syscompfragments".
DBCC results for 'sys.sysftstops'.
There are 0 rows in 0 pages for object "sys.sysftstops".
DBCC results for 'sys.sysqnames'.
There are 97 rows in 1 pages for object "sys.sysqnames".
DBCC results for 'sys.sysxmlcomponent'.
There are 99 rows in 1 pages for object "sys.sysxmlcomponent".
DBCC results for 'sys.sysxmlfacet'.
There are 112 rows in 1 pages for object "sys.sysxmlfacet".
DBCC results for 'sys.sysxmlplacement'.
There are 18 rows in 1 pages for object "sys.sysxmlplacement".
DBCC results for 'sys.sysobjkeycrypts'.
There are 0 rows in 0 pages for object "sys.sysobjkeycrypts".
DBCC results for 'sys.sysasymkeys'.
There are 0 rows in 0 pages for object "sys.sysasymkeys".
DBCC results for 'sys.syssqlguides'.
There are 0 rows in 0 pages for object "sys.syssqlguides".
DBCC results for 'sys.sysbinsubobjs'.
There are 3 rows in 1 pages for object "sys.sysbinsubobjs".
DBCC results for 'sys.syssoftobjrefs'.
There are 3630 rows in 56 pages for object "sys.syssoftobjrefs".
DBCC results for 'Roles'.
There are 100 rows in 4 pages for object "Roles".
DBCC results for 'NameValuePair_Greek_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Greek_CI_AS".
DBCC results for 'AllDocs'.
There are 77095 rows in 4766 pages for object "AllDocs".
DBCC results for 'NameValuePair_Hebrew_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Hebrew_CI_AS".
DBCC results for 'RoleAssignment'.
There are 7398 rows in 56 pages for object "RoleAssignment".
DBCC results for 'NameValuePair_Hindi_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Hindi_CI_AS".
DBCC results for 'NameValuePair_Hungarian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Hungarian_CI_AS".
DBCC results for 'NameValuePair_Hungarian_Technical_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Hungarian_Technical_CI_AS".
DBCC results for 'NameValuePair_Icelandic_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Icelandic_CI_AS".
DBCC results for 'NameValuePair_Japanese_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Japanese_CI_AS".
DBCC results for 'NameValuePair_Japanese_Unicode_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Japanese_Unicode_CI_AS".
DBCC results for 'AllDocStreams'.
Repair: The Clustered index successfully rebuilt for the object "dbo.AllDocStreams" in database "Techshare_Content".
Repair: The page (1:713625) has been deallocated from object ID 261575970, index ID 1, partition ID 72057599060803584, alloc unit ID 72057594043826176 (type LOB data).
Repair: The page (1:713626) has been deallocated from object ID 261575970, index ID 1, partition ID 72057599060803584, alloc unit ID 72057594043826176 (type LOB data).
Repair: The page (1:713627) has been deallocated from object ID 261575970, index ID 1, partition ID 72057599060803584, alloc unit ID 72057594043826176 (type LOB data).
Repair: Deleted record for object ID 261575970, index ID 1, partition ID 72057599060803584, alloc unit ID 72057599189450752 (type In-row data), on page (1:1438044), slot 62. Indexes will be rebuilt.
Repair: Deleted off-row data column with ID 85432795136, for object ID 261575970, index ID 1, partition ID 72057599060803584, alloc unit ID 72057599189450752 (type In-row data) on page (1:1438044), slot 62.
Repair: The Nonclustered index successfully rebuilt for the object "dbo.AllDocStreams, AllDocStreams_DeleteTransactionIdIdLevelUnique" in database "Techshare_Content".
Repair: The Nonclustered index successfully rebuilt for the object "dbo.AllDocStreams, AllDocStreams_IdLevelUnique" in database "Techshare_Content".
Repair: The Nonclustered index successfully rebuilt for the object "dbo.AllDocStreams, AllDocStreams_SiteIdId" in database "Techshare_Content".
Msg 8945, Level 16, State 1, Line 1
Table error: Object ID 261575970, index ID 1 will be rebuilt.
The error has been repaired.
Msg 8928, Level 16, State 1, Line 1
Object ID 261575970, index ID 1, partition ID 72057599060803584, alloc unit ID 72057594043826176 (type LOB data): Page (1:713625) could not be processed. See other errors for details.
The error has been repaired.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 261575970, index ID 1, partition ID 72057599060803584, alloc unit ID 72057594043826176 (type LOB data), page (1:713625). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 146802697 and -4.
The error has been repaired.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 261575970, index ID 1, partition ID 72057599060803584, alloc unit ID 72057594043826176 (type LOB data). The off-row data node at page (1:713625), slot 0, text ID 85432795136 is referenced by page (1:74024), slot 0, but was not seen in the scan.
The error has been repaired.
Msg 8928, Level 16, State 1, Line 1
Object ID 261575970, index ID 1, partition ID 72057599060803584, alloc unit ID 72057594043826176 (type LOB data): Page (1:713626) could not be processed. See other errors for details.
The error has been repaired.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 261575970, index ID 1, partition ID 72057599060803584, alloc unit ID 72057594043826176 (type LOB data), page (1:713626). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 146802697 and -4.
The error has been repaired.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 261575970, index ID 1, partition ID 72057599060803584, alloc unit ID 72057594043826176 (type LOB data). The off-row data node at page (1:713626), slot 0, text ID 85432795136 is referenced by page (1:74024), slot 0, but was not seen in the scan.
The error has been repaired.
Msg 8928, Level 16, State 1, Line 1
Object ID 261575970, index ID 1, partition ID 72057599060803584, alloc unit ID 72057594043826176 (type LOB data): Page (1:713627) could not be processed. See other errors for details.
The error has been repaired.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 261575970, index ID 1, partition ID 72057599060803584, alloc unit ID 72057594043826176 (type LOB data), page (1:713627). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 146802697 and -4.
The error has been repaired.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 261575970, index ID 1, partition ID 72057599060803584, alloc unit ID 72057594043826176 (type LOB data). The off-row data node at page (1:713627), slot 0, text ID 85432795136 is referenced by page (1:74024), slot 0, but was not seen in the scan.
The error has been repaired.
Msg 8929, Level 16, State 1, Line 1
Object ID 261575970, index ID 1, partition ID 72057599060803584, alloc unit ID 72057599189450752 (type In-row data): Errors found in off-row data with ID 85432795136 owned by data record identified by RID = (1:1438044:62)
The error has been repaired.
Msg 8945, Level 16, State 1, Line 1
Table error: Object ID 261575970, index ID 2 will be rebuilt.
The error has been repaired.
Msg 8945, Level 16, State 1, Line 1
Table error: Object ID 261575970, index ID 3 will be rebuilt.
The error has been repaired.
Msg 8945, Level 16, State 1, Line 1
Table error: Object ID 261575970, index ID 6 will be rebuilt.
The error has been repaired.
There are 11947 rows in 157 pages for object "AllDocStreams".
CHECKDB found 0 allocation errors and 10 consistency errors in table 'AllDocStreams' (object ID 261575970).
CHECKDB fixed 0 allocation errors and 10 consistency errors in table 'AllDocStreams' (object ID 261575970).
DBCC results for 'NameValuePair_Korean_Wansung_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Korean_Wansung_CI_AS".
DBCC results for 'NameValuePair_Korean_Wansung_Unicode_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Korean_Wansung_Unicode_CI_AS".
DBCC results for 'NameValuePair_Latin1_General_CI_AS'.
There are 597 rows in 10 pages for object "NameValuePair_Latin1_General_CI_AS".
DBCC results for 'NameValuePair_Latvian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Latvian_CI_AS".
DBCC results for 'AllDocVersions'.
There are 24221 rows in 351 pages for object "AllDocVersions".
DBCC results for 'NameValuePair_Lithuanian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Lithuanian_CI_AS".
DBCC results for 'NameValuePair_Lithuanian_Classic_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Lithuanian_Classic_CI_AS".
DBCC results for 'NameValuePair_Traditional_Spanish_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Traditional_Spanish_CI_AS".
DBCC results for 'AllLinks'.
There are 124297 rows in 7514 pages for object "AllLinks".
DBCC results for 'NameValuePair_Modern_Spanish_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Modern_Spanish_CI_AS".
DBCC results for 'DatabaseInformation'.
There are 2 rows in 1 pages for object "DatabaseInformation".
DBCC results for 'NameValuePair_Polish_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Polish_CI_AS".
DBCC results for 'NavNodes'.
There are 2806 rows in 61 pages for object "NavNodes".
DBCC results for 'NameValuePair_Romanian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Romanian_CI_AS".
DBCC results for 'RecycleBin'.
There are 1093 rows in 62 pages for object "RecycleBin".
DBCC results for 'NameValuePair_Slovak_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Slovak_CI_AS".
DBCC results for 'Sites'.
There are 3 rows in 1 pages for object "Sites".
DBCC results for 'NameValuePair_Slovenian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Slovenian_CI_AS".
DBCC results for 'NameValuePair_Thai_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Thai_CI_AS".
DBCC results for 'NameValuePair_Turkish_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Turkish_CI_AS".
DBCC results for 'NameValuePair_Ukrainian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Ukrainian_CI_AS".
DBCC results for 'Image0x'.
There are 1 rows in 1 pages for object "Image0x".
DBCC results for 'NameValuePair_Vietnamese_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Vietnamese_CI_AS".
DBCC results for 'WebPartLists'.
There are 14217 rows in 207 pages for object "WebPartLists".
DBCC results for 'WebParts'.
There are 12122 rows in 327 pages for object "WebParts".
DBCC results for 'HT_Settings'.
There are 5 rows in 1 pages for object "HT_Settings".
DBCC results for 'HT_Cache'.
There are 0 rows in 0 pages for object "HT_Cache".
DBCC results for 'SiteVersions'.
There are 23 rows in 1 pages for object "SiteVersions".
DBCC results for 'Webs'.
There are 198 rows in 148 pages for object "Webs".
DBCC results for 'Features'.
There are 6028 rows in 74 pages for object "Features".
DBCC results for 'EventBatches'.
There are 1 rows in 1 pages for object "EventBatches".
DBCC results for 'EventCache'.
There are 10617 rows in 498 pages for object "EventCache".
DBCC results for 'EventLog'.
There are 1057 rows in 44 pages for object "EventLog".
DBCC results for 'EventSubsMatches'.
There are 0 rows in 0 pages for object "EventSubsMatches".
DBCC results for 'ImmedSubscriptions'.
There are 452 rows in 85 pages for object "ImmedSubscriptions".
DBCC results for 'Categories'.
There are 0 rows in 0 pages for object "Categories".
DBCC results for 'WebCat'.
There are 2376 rows in 24 pages for object "WebCat".
DBCC results for 'AllLists'.
There are 1790 rows in 139 pages for object "AllLists".
DBCC results for 'SchedSubscriptions'.
There are 14 rows in 3 pages for object "SchedSubscriptions".
DBCC results for 'Personalization'.
There are 56 rows in 2 pages for object "Personalization".
DBCC results for 'WelcomeNames'.
There are 2 rows in 1 pages for object "WelcomeNames".
DBCC results for 'TimerLock'.
There are 1 rows in 1 pages for object "TimerLock".
DBCC results for 'AllUserData'.
There are 79601 rows in 10788 pages for object "AllUserData".
DBCC results for 'DiskWarningDate'.
There are 1 rows in 1 pages for object "DiskWarningDate".
DBCC results for 'Workflow'.
There are 519 rows in 21 pages for object "Workflow".
DBCC results for 'WorkflowAssociation'.
There are 1450 rows in 112 pages for object "WorkflowAssociation".
DBCC results for 'sys.filestream_tombstone_1483920408'.
There are 0 rows in 0 pages for object "sys.filestream_tombstone_1483920408".
DBCC results for 'sys.syscommittab'.
There are 0 rows in 0 pages for object "sys.syscommittab".
DBCC results for 'ScheduledWorkItems'.
There are 3 rows in 1 pages for object "ScheduledWorkItems".
DBCC results for 'ComMd'.
There are 0 rows in 0 pages for object "ComMd".
DBCC results for 'EventReceivers'.
There are 10899 rows in 528 pages for object "EventReceivers".
DBCC results for 'NameValuePair'.
There are 1152 rows in 17 pages for object "NameValuePair".
DBCC results for 'ContentTypes'.
There are 1450 rows in 17 pages for object "ContentTypes".
DBCC results for 'NameValuePair_Albanian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Albanian_CI_AS".
DBCC results for 'NameValuePair_Arabic_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Arabic_CI_AS".
DBCC results for 'AuditData'.
There are 1326811 rows in 37162 pages for object "AuditData".
DBCC results for 'SiteQuota'.
There are 0 rows in 0 pages for object "SiteQuota".
DBCC results for 'NameValuePair_Chinese_PRC_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Chinese_PRC_CI_AS".
DBCC results for 'ContentTypeUsage'.
There are 33378 rows in 420 pages for object "ContentTypeUsage".
DBCC results for 'NameValuePair_Chinese_PRC_Stroke_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Chinese_PRC_Stroke_CI_AS".
DBCC results for 'NameValuePair_Chinese_Taiwan_Bopomofo_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Chinese_Taiwan_Bopomofo_CI_AS".
DBCC results for 'BuildDependencies'.
There are 5489 rows in 181 pages for object "BuildDependencies".
DBCC results for 'CollationNames'.
There are 39 rows in 1 pages for object "CollationNames".
DBCC results for 'NameValuePair_Chinese_Taiwan_Stroke_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Chinese_Taiwan_Stroke_CI_AS".
DBCC results for 'AllUserDataJunctions'.
There are 1324 rows in 36 pages for object "AllUserDataJunctions".
DBCC results for 'NameValuePair_Croatian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Croatian_CI_AS".
DBCC results for 'NameValuePair_Cyrillic_General_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Cyrillic_General_CI_AS".
DBCC results for 'NameValuePair_Czech_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Czech_CI_AS".
DBCC results for 'UserInfo'.
There are 1430 rows in 54 pages for object "UserInfo".
DBCC results for 'NameValuePair_Danish_Norwegian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Danish_Norwegian_CI_AS".
DBCC results for 'SiteDeletion'.
There are 0 rows in 0 pages for object "SiteDeletion".
DBCC results for 'sys.queue_messages_1977058079'.
There are 0 rows in 0 pages for object "sys.queue_messages_1977058079".
DBCC results for 'NameValuePair_Estonian_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Estonian_CI_AS".
DBCC results for 'WebMembers'.
There are 19932 rows in 89 pages for object "WebMembers".
DBCC results for 'sys.queue_messages_2009058193'.
There are 0 rows in 0 pages for object "sys.queue_messages_2009058193".
DBCC results for 'NameValuePair_Finnish_Swedish_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Finnish_Swedish_CI_AS".
DBCC results for 'Perms'.
There are 275 rows in 7 pages for object "Perms".
DBCC results for 'sys.queue_messages_2041058307'.
There are 0 rows in 0 pages for object "sys.queue_messages_2041058307".
DBCC results for 'NameValuePair_French_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_French_CI_AS".
DBCC results for 'Versions'.
There are 8 rows in 1 pages for object "Versions".
DBCC results for 'Groups'.
There are 200 rows in 7 pages for object "Groups".
DBCC results for 'NameValuePair_Georgian_Modern_Sort_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_Georgian_Modern_Sort_CI_AS".
DBCC results for 'NameValuePair_German_PhoneBook_CI_AS'.
There are 0 rows in 0 pages for object "NameValuePair_German_PhoneBook_CI_AS".
DBCC results for 'Deps'.
There are 894 rows in 42 pages for object "Deps".
DBCC results for 'GroupMembership'.
There are 1224 rows in 7 pages for object "GroupMembership".
CHECKDB found 0 allocation errors and 10 consistency errors in database 'database name'.
CHECKDB fixed 0 allocation errors and 10 consistency errors in database 'database name'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
A big thank you to everyone who contributed to the thread. We really appreciate the suggestions and all the help.
August 18, 2010 at 6:37 pm
I ran the statement:
dbcc traceon (3604)
go
dbcc page (yourdbname, 1,11368905,3)
go
This is what returned:
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Msg 8968, Level 16, State 1, Line 1
Table error: DBCC PAGE page (1:11368905) (object ID 0, index ID 0, partition ID 0, alloc unit ID 0 (type Unknown)) is out of the range of this database.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
What does "out of the range of this database" mean?
Viewing 15 posts - 1 through 15 (of 15 total)
You must be logged in to reply to this topic. Login to reply