May 1, 2012 at 9:36 pm
Hi All
Since the network engineer upgraded the virutal server SAN software two weeks ago the sharepoint database has been failing the nightly database integrity check. The error log and sqlserver log shows the following entries.
-----
BCC CHECKDB (WSS_Content_xxx) WITH no_infomsgs executed by dbadmin terminated abnormally due to error state 5. Elapsed time: 0 hours 2 minutes 17 seconds.
-----
Error number 1073548784
-------------
The database seems okay in that it can backup, etc, but it fails the Integrity Check.
Any suggestions would be welcome.
Adonia
May 1, 2012 at 10:46 pm
There should be more to the error message than just that. Check the SQL Log to see if there is more info there. Also, what OS are you running?
May 1, 2012 at 11:11 pm
OS is Windows Server 2008 R2 SP1. The only other entries in the sql logs is
-----
Source MSSQL$SHAREPOINT
Category Server
Event 3221243525
Computer sql.business.local
Message
Error: 17312, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
----------------------------
THanks in Advance Adonia
May 1, 2012 at 11:59 pm
Is it generating mini-dumps when this error occurs? Are you able to manually create a snapshot of the database? If so, try running CheckDB on the snapshot and let us know how that goes.
May 2, 2012 at 12:49 am
Please run the following and post the full and complete results
DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
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
May 7, 2012 at 8:53 pm
The message returned is below, but I needed to use the database_id as some silly sausage used -hypens in the database name which returns a syntax error for the above dbcc checkdb command.
I added space to the tempdb and there are no previous error messages.
------------------------
Msg 8921, Level 16, State 1, Line 2
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 802, Level 17, State 20, Line 2
Error: 802, Severity: 17, State: 20. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
May 7, 2012 at 9:16 pm
I thought I'd run the checkdb with infomsgs since I'm not getting anything back in the error logs. Does this mean there is a problem or not ? ANd how can I fix it ??
Thanks Adonia
--------------------------------------------------
DBCC results for 'WSS_Content_8e01f4f2-eabb-404f-939e-90d3b9a633dc'.
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.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'WSS_Content_8e01f4f2-eabb-404f-939e-90d3b9a633dc'.
Msg 802, Level 17, State 20, Line 1
Error: 802, Severity: 17, State: 20. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped
May 7, 2012 at 10:12 pm
Sounds like it may be a problem that is causing the snapshot to fail. Can you try running CheckDB with the TABLOCK option?
DBCC CHECKDB ('WSS_Content_8e01f4f2-eabb-404f-939e-90d3b9a633dc') WITH TABLOCK, ALL_ERRORMSGS, NO_INFOMSGS;
May 7, 2012 at 10:29 pm
Hi I can't run this at the moment as it's a live prod db,but I'm organising a bak copy to be moved to my test instance. Will let you know once all done.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply