<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2005
»
Data Corruption
»
Stack Dump in Error Log
14 posts, Page 1 of 2
1
2
»»
Stack Dump in Error Log
Rate Topic
Display Mode
Topic Options
Author
Message
montgomerybrothers
montgomerybrothers
Posted Monday, April 13, 2009 9:21 AM
Grasshopper
Group: General Forum Members
Last Login: Friday, May 21, 2010 9:53 AM
Points: 15,
Visits: 48
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
Paul Randal
Paul Randal
Posted Monday, April 13, 2009 9:32 AM
SSCommitted
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 1:23 PM
Points: 1,905,
Visits: 1,601
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
montgomerybrothers
montgomerybrothers
Posted Monday, April 13, 2009 10:04 AM
Grasshopper
Group: General Forum Members
Last Login: Friday, May 21, 2010 9:53 AM
Points: 15,
Visits: 48
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
Paul Randal
Paul Randal
Posted Monday, April 13, 2009 10:20 AM
SSCommitted
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 1:23 PM
Points: 1,905,
Visits: 1,601
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
montgomerybrothers
montgomerybrothers
Posted Monday, April 13, 2009 10:39 AM
Grasshopper
Group: General Forum Members
Last Login: Friday, May 21, 2010 9:53 AM
Points: 15,
Visits: 48
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
Paul Randal
Paul Randal
Posted Monday, April 13, 2009 10:48 AM
SSCommitted
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 1:23 PM
Points: 1,905,
Visits: 1,601
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
montgomerybrothers
montgomerybrothers
Posted Monday, April 13, 2009 11:21 AM
Grasshopper
Group: General Forum Members
Last Login: Friday, May 21, 2010 9:53 AM
Points: 15,
Visits: 48
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
Paul Randal
Paul Randal
Posted Monday, April 13, 2009 11:24 AM
SSCommitted
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 1:23 PM
Points: 1,905,
Visits: 1,601
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
Paul Randal
Paul Randal
Posted Monday, April 13, 2009 11:46 AM
SSCommitted
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 1:23 PM
Points: 1,905,
Visits: 1,601
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
montgomerybrothers
montgomerybrothers
Posted Monday, April 13, 2009 12:11 PM
Grasshopper
Group: General Forum Members
Last Login: Friday, May 21, 2010 9:53 AM
Points: 15,
Visits: 48
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 »
14 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
