July 7, 2008 at 7:14 am
Hi,
I have a peculiar problem while querying a table in my database.
I get the following error when executing any commands against a particular table.
Msg 211, Level 23, State 51, Line 1
Possible schema corruption. Run DBCC CHECKCATALOG.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Query against all other tables work fine.
DBCC CHECKCATALOG runs fine with the below message.
DBCC execution completed. If DBCC printed error message, contact your system administrator.
DBCC CHECKTABLE, DBCC CHECKDB gives the following error
Msg 211, Level 23, State 51, Line 1
Possible schema corruption. Run DBCC CHECKCATALOG.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
DBCC CHECKALLOC returns the following message.
DBCC results for 'tharves'.
CHECKALLOC found 0 allocation errors and 0 consistency errors in database 'tharves'.
Msg 211, Level 23, State 51, Line 1
Possible schema corruption. Run DBCC CHECKCATALOG.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Any pointers to fix this problem please....
Cheers,
Imran.
July 7, 2008 at 7:16 am
Is there anything useful in the SQL Error log?
Do you have a backup from before this started?
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
July 7, 2008 at 8:54 am
You need to call Microsoft for this. Catalog errors can have serious effects on your database.
July 7, 2008 at 11:18 am
I do not have much in the error logs and I don't have a backup of the database before this error popped up.
The only noticeable thing that happens is, SQL Server does a stack dump everytime before popping up this error message.
July 7, 2008 at 2:16 pm
Your database is corrupt and cannot be repaired (DBCC CHECKDB won't run, so you can't run repair). I just demo'd these errors at TechEd in June.
Given that you have no backup, and you can't run repair, you have no choice but to extract as much data as you can into a new database. Not sure how far you'll get with this as the database has system catalog corruption but's bad enough that CHECKDB can't get past it.
And get a backup strategy.
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
September 1, 2008 at 2:39 am
Thx for your info Paul.
Could we give me details on how does this happen? or the way to simulate the same error?
thanks!
September 1, 2008 at 3:02 am
Generally corruption is a hardware issue (Io subsystem). See -
http://www.sqlskills.com/blogs/paul/2008/08/27/SearchEngineQA26MythsAroundCausingCorruption.aspx
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 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply