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

DBCC CHECKDB('master') gives no errors in log, but generates Msg 0 (severe error, discard results) Expand / Collapse
Author
Message
Posted Tuesday, January 15, 2013 10:06 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: Wednesday, October 1, 2014 8:20 AM
Points: 932, Visits: 368
Our weekly integrity check job on one of our servers has now failed two weeks in a row. In both cases, the only database known to be generating an error is the 'master' db.

If I run the DBCC CHECKDB('master') command manually, I get the same results. The log shows no errors, and that the DB is A-OK. The output to the console of the command indicates the same. However, instead of the final line about errors reported by DBCC (as you see here, when I run the command against msdb):
CHECKDB found 0 allocation errors and 0 consistency errors in database 'msdb'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.


I get Msg 0:
CHECKDB found 0 allocation errors and 0 consistency errors in database 'master'.
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.


Naturally, as it appears the results that should be discarded are the ones that say the DB is fine, I'm in a bit of a quandary.

The database has not been restarted since I first saw the error; I'll be requesting one today.

The databases on the server all seem to be behaving normally.

Our external DBA team has recommended updating the server (SQL 2008, SP2, version 10.00.4279) to SP2 cumulative update 7, as that is supposed to fix a situation where you get this message running DBCC CHECKDB on a DB/table with a spatial index. While I don't mind updating (I'd actually have them go to SP3, CU3), this looks like a "hail Mary" play to me.

So:

1. Is it likely that I actually have a corrupt DB?

2. Noting that we'd install the CU on two other servers that have no symptoms before we'd get to the production box that does - does it seem at all likely that SP2CU7 (or SP3CU3) will actually fix the problem?

3. Is there something else I should be looking at/checking on?

Thanks in advance for your advice.



R David Francis
Post #1407356
Posted Wednesday, January 16, 2013 2:54 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Monday, October 13, 2014 6:42 AM
Points: 5,216, Visits: 5,111
What is the full output from DBCC CHECKDB .... ALL_ERRORMSGS, NO_INFOMSGS



Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1407707
Posted Wednesday, January 16, 2013 4:11 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Today @ 4:14 AM
Points: 709, Visits: 1,430
Curious if SQL had problems writing to the error log. Can you cycle the error log and try again?

EXEC sp_cycle_errorlog


Joie Andrew
"Since 1982"
Post #1407732
Posted Wednesday, January 16, 2013 4:33 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 10:23 AM
Points: 2,008, Visits: 3,434
CHECKDB on master also runs CHECKDB on the resource database, not sure if the errors are coming from that rather than master.
I get errors from running CHECKDB on a restored copy of master attached as a user db on another server, but that's error 8906.
Post #1407740
Posted Friday, January 18, 2013 3:53 PM


SSC Eights!

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

Group: General Forum Members
Last Login: Wednesday, October 1, 2014 8:20 AM
Points: 932, Visits: 368
The full and complete output of DBCC CHECKDB('master') WITH all_errormsgs, no_infomsgs is, excitingly enough:

Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.



R David Francis
Post #1409128
Posted Friday, January 18, 2013 3:56 PM


SSC Eights!

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

Group: General Forum Members
Last Login: Wednesday, October 1, 2014 8:20 AM
Points: 932, Visits: 368
Our regular job recycled the error log last night; the output in the previous message was generated 5 minutes ago.

The SQL Server log just shows this:

DBCC CHECKDB (master) WITH all_errormsgs, no_infomsgs executed by Us\DFrancis found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 4 seconds. Internal database snapshot has split point LSN = 00000989:000000d8:0002 and first LSN = 00000989:000000d0:0001.

[edited to improve formatting]



R David Francis
Post #1409129
Posted Monday, January 21, 2013 1:45 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 4:16 AM
Points: 121, Visits: 1,248
Please check this article: http://blog.sqlauthority.com/2008/02/19/sql-server-2005-fix-error-message-when-you-run-a-query-against-a-table-that-does-not-have-a-clustered-index-in-sql-server-2005-a-severe-error-occurred-on-the-current-command/

Hope it will help you to resolve your issue..


SQL Database Recovery Expert
Post #1409410
Posted Monday, January 21, 2013 1:45 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 4:16 AM
Points: 121, Visits: 1,248
Hope it will help you to resolve your issue..

SQL Database Recovery Expert
Post #1409411
Posted Wednesday, January 23, 2013 10:01 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: Wednesday, October 1, 2014 8:20 AM
Points: 932, Visits: 368
I'm pretty sure that I've already got any fix from SQL 2005 SP2 CU6 (released on 2008-02-18) in my SQL 2008 SP2 (released 2010-09-24). Thanks anyway...


R David Francis
Post #1410693
Posted Wednesday, January 23, 2013 10:11 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: Wednesday, October 1, 2014 8:20 AM
Points: 932, Visits: 368
So, an update. We did get the server restarted over the weekend. In fact, we also got a disk drive replaced and the OS rebuilt. One supposes that sort of thing could have an impact on this. Following all this, our weekly Integrity Check job completed without errors, and explicitly running DBCC CHECKDB('master') runs as expected, and doesn't tell me to throw out my results.

Hopefully, that resolves my issue. Thanks all for your assistance!



R David Francis
Post #1410697
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse