stack dumps

Question

stack dumps

HildaJ

SSCarpal Tunnel

Points: 4516
More actions
July 1, 2013 at 8:43 am

#295220

I'm running integrity checks on my databases and a couple of days ago I started seeing this job failed. It's basically:
USE [database]
GO
DBCC CHECKDB(N'database') WITH NO_INFOMSGS
When I ran the script above manually I get:
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
I'm also getting files created under the logs directory with stack dumps. I'm not experience with this problem, I haven't actually gone through something like this. What does it mean? How do I start troubleshooting it? How do I fix it?
Thank you.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

sqlSherwin SSCrazy Points: 2884 More actions · Answer 1

CHECKDB is encountering a severe error that is preventing it from completing. You may be able to get the actual error by running DBCC CHECKCATALOG but I suggest you recover your database using a backup anyway.

HildaJ SSCarpal Tunnel Points: 4516 More actions · Answer 2

I ran a DBCC CHECKALLOC(database) and DBBC CHECKCATALOG(database), both commands ran without any errors.

It has been a couple of backup since we started getting this error, if we restore one of those backups, would we still be seeing those errors? I guess my question is the errors are related to the database or the actual location where the database resides (hardware I mean)? If we store wouldn't we still see those errors?

sqlSherwin SSCrazy Points: 2884 More actions · Answer 3

Yes, you will need to restore from a backup that does not contain these errors otherwise you will continue to see the error after restoring.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 4

Anything relevant in the SQL error logs?

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

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

HildaJ SSCarpal Tunnel Points: 4516 More actions · Answer 5

I'm looking through all my logs and going back further.

I did a quick test on my personal machine that run sql server. I ran a backup of the database on the production server and restored it on my PC. Ran a few quick tests. I created a mainteance plan with the following tasks:

-- check db integrity (DBCC CHECKDB)

-- a reorganized index task

-- update stats

It successfully ran fine. No errors. That gives me hope.

I looked at those stack dump files back from a month ago and I found this information:

2013-03-20 09:28:57.35 Server Using 'dbghelp.dll' version '4.0.5'

2013-03-20 09:28:57.38 Server ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0001.txt

2013-03-20 09:28:57.38 Server SqlDumpExceptionHandler: Process 1732 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

2013-03-20 09:28:57.38 Server * *******************************************************************************

2013-03-20 09:28:57.38 Server *

2013-03-20 09:28:57.38 Server * BEGIN STACK DUMP:

2013-03-20 09:28:57.38 Server * 03/20/13 09:28:57 spid 1732

2013-03-20 09:28:57.38 Server *

.... other dump files have

**Dump thread - spid = 0, EC = 0x0000000000000000

***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0003.tx

t

* *******************************************************************************

*

* BEGIN STACK DUMP:

* 03/20/13 09:29:29 spid 2608

*

* A fatal error occurred in .NET Framework runtime.

*

I'm not familiar and have not experience,nothing is making sense. I'm still digging. Any help is very appreciated.

Thanks.

2013-03-20 09:28:57.38 Server *

2013-03-20 09:28:57.38 Server * Exception Address = 0000000002A4D404 Module(sqlservr+000000000255D404)

2013-03-20 09:28:57.38 Server * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION

2013-03-20 09:28:57.38 Server * Access Violation occurred reading address 0000000000001DB0

2013-03-20 09:28:57.38 Server *

2013-03-20 0

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 6

I'd call Customer Support at this point.

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

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