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 12»»

Stack Dump in Error Log Expand / Collapse
Author
Message
Posted Monday, April 13, 2009 9:21 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, May 29, 2013 3:50 AM
Points: 16, Visits: 51
Hello,

I am not sure where to post this question or all the details you might need. It has been a while since I worked with SQL, but after some recent problems I am now the one who has the responsibility.

I am working with a Win2K3 Enterprise sp2 and SQL 2005 sp2 in a Virtual environment. We had a problem a few days ago where the VM image did not successfully complete a snapshot cleanup. When we got the server back up, I had server DBs in suspect mode or showed errors during the maintenance. I restored those DBs and everything looks clean. Except, I see in the errorlog a reference to a stack dump. I really don't see where it tells me which database is the problem. The only real error I see is this one; "Error: 211, Severity: 23, State: 51".
I have been trying to search the web/this forum to find any similar issues, so I might understand where to look next. Any help that you can point me in would be greatly appreciated.

Thank you,
Monty



Post #695886
Posted Monday, April 13, 2009 9:32 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Sunday, August 3, 2014 11:47 AM
Points: 2,038, Visits: 1,664
This error and state indicates that you've got missing information in one of the system tables in a database (i.e. metadata corruption). In the SQL Server error log (buried down in the LOG directory) you should be able to see which database is giving the problem. After that, you should be able to restore the database (sounds like you have backups).

Does that help?


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
Post #695893
Posted Monday, April 13, 2009 10:04 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, May 29, 2013 3:50 AM
Points: 16, Visits: 51
Paul Randal (4/13/2009)
This error and state indicates that you've got missing information in one of the system tables in a database (i.e. metadata corruption). In the SQL Server error log (buried down in the LOG directory) you should be able to see which database is giving the problem. After that, you should be able to restore the database (sounds like you have backups).

Does that help?


Thanks Paul, it sort of helps. I can understand that a system table is messed up, but where in the error log should it say the DB? You dp mean the errorlog and not one of the stackdumpxxxx.log, stackdumpxxx.txt, or stackdumpxxxx.mdmp? In the errorlog, right before the stack dump output I see this line;
2009-04-11 20:30:27.08 spid56 DBCC CHECKDB (mssqlsystemresource) WITH no_infomsgs executed by NT AUTHORITY\SYSTEM found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.
-----
after the stack dump I see this line;
2009-04-11 20:36:38.46 Backup Database backed up. Database: master, creation date(time): 2009/04/08(20:33:52), pages dumped: 371, first LSN: 1703:320:37, last LSN: 1703:344:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'D:\master.bak'}). This is an informational message only. No user action is required.

Just not sure where to find the db name?



Post #695921
Posted Monday, April 13, 2009 10:20 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Sunday, August 3, 2014 11:47 AM
Points: 2,038, Visits: 1,664
Should be somewhere in there - can you post the error log? (Or just email it to me - paul@sqlskills.com).

It's entirely possible (and likely) that the error came from one of the suspect databases that you've already restored. Have you run DBCC CHECKDB on all the databases since you restored them?


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
Post #695927
Posted Monday, April 13, 2009 10:39 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, May 29, 2013 3:50 AM
Points: 16, Visits: 51
Paul Randal (4/13/2009)
Should be somewhere in there - can you post the error log? (Or just email it to me - paul@sqlskills.com).

It's entirely possible (and likely) that the error came from one of the suspect databases that you've already restored. Have you run DBCC CHECKDB on all the databases since you restored them?


Paul,

I will email you a copy of my log.
The DBs were restored last Wednesday and I have a sql maintenance job setup to run nightly. I am running the DBCCs that run when you select the DBCC in a maintenance plan, so I hope that they are right. I see all the DBs look good as far as that sql maintenance output file, but I'm still seeing the stack dump error in the log every night that the maintenance script runs.



Post #695939
Posted Monday, April 13, 2009 10:48 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Sunday, August 3, 2014 11:47 AM
Points: 2,038, Visits: 1,664
Ah - ok you've definitely still got a corrupt database then. Do you have any output from the maintenance job(s)? One of them should be failing every night...

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
Post #695951
Posted Monday, April 13, 2009 11:21 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, May 29, 2013 3:50 AM
Points: 16, Visits: 51
Paul Randal (4/13/2009)
Ah - ok you've definitely still got a corrupt database then. Do you have any output from the maintenance job(s)? One of them should be failing every night...


Hey Paul,

I sent a copy of the errorlog and the last maintenance output file to your email address.

Thanks
Monty



Post #695972
Posted Monday, April 13, 2009 11:24 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Sunday, August 3, 2014 11:47 AM
Points: 2,038, Visits: 1,664
Got 'em.

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
Post #695975
Posted Monday, April 13, 2009 11:46 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Sunday, August 3, 2014 11:47 AM
Points: 2,038, Visits: 1,664
Ok - first problems is that you're running vanilla SP2, which has a bunch of bugs in maintenance plans. From the output you've sent, you're hitting the one where it repeatedly CHECKDBs master instead of the actual user database. You need to install the hotfix described in http://support.microsoft.com/kb/934459 to fix that. Then you'll *really* be running DBCC CHECKDB against the user databases.

Once you've done that and CHECKDB runs, we'll see which database has the corruption.

The stack dump looks to be coming from the cleanup part of your maintenance task, and there was also a bug there too - so the hotfix I've pointed you at above might resolve that too (it fixes the cleanup task bug).

Thanks


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
Post #695990
Posted Monday, April 13, 2009 12:11 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, May 29, 2013 3:50 AM
Points: 16, Visits: 51
Thanks Paul,

As I was downloading the patch, I see that SP3 is out there. What do you think of that? Has there been any issues with that patch? Would that also resolve my problem?



Post #696020
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse