April 27, 2009 at 6:15 am
Hi all, i have a database with 300 GB. So we have this error :
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x9e5067f7; actual: 0x3c37c822). It occurred during a read of page (4:1348873) in database ID 5 at offset 0x00000292a12000 in file 'I:\dbBR_ZipCode\dbBR_Aux.ndf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Before iuse dbcc checkdb i want to use dbcc page with tableresult , because if somenthing happened we have this infomormation..but when i try dbcc page (database,4,1348873,3) this errors appears
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
And disconnect..
We dont have a backup. There´s other way to do this ?..or i have to use dbcc checkdb and wait...
Thanks a lot
April 27, 2009 at 6:26 am
Run DBCC CHECKDB - it's the only thing that will tell you how corrupt your database is. And start taking backups - so you don't lose data when corruption occurs, as it does inevitably.
If you don't have a backup, you may end up losing data because you have no other way to recover apart from running DBCC CHECKDB with a repair option - which usually means deleting corrupt data.
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
April 27, 2009 at 6:30 am
April 27, 2009 at 6:37 am
Ha - CHECKDB From Every Angle: How long will CHECKDB take to run?
CHECKDB will tell you the option to use - most likely REPAIR_ALLOW_DATA_LOSS.
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
April 27, 2009 at 6:54 am
April 27, 2009 at 10:08 am
If, after you've got the checkDB results, you're not 100% sure what they mean or what you need to do, post the full output of checkDB and someone will help you interpret it.
Also, take a look at this article. http://www.sqlservercentral.com/articles/65804/
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
April 28, 2009 at 6:03 am
April 28, 2009 at 8:14 am
Gail/Paul
If i run the dbcc checkdb only to see what i have to do (i understand i have to run first and the dbcc tell me what to do..what option i need to use) ...i have 194 GB.
Paul sends to me one link about dbcc run time ..but i dont know if was when i run dbcc checdb with corrections options or dbcc checkdb only to see what i have to do .
this will be faster ?..run dbcc only to know what it say...?
April 28, 2009 at 8:22 am
Laerte POltronieri Junior (4/28/2009)
Paul sends to me one link about dbcc run time ..but i dont know if was when i run dbcc checdb with corrections options or dbcc checkdb only to see what i have to do .
The latter. To see the details of what's wrong.
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
April 28, 2009 at 8:26 am
So I think in my case, 194 GB. it will be log duration ok ?..
I have a windows somenthing like 10:00 PM and 6:00 AM.. with you experience...i can do in this window ?..because the system in online yet..2 tables have problems..but i cant stop much time because the other tables is very used.
April 28, 2009 at 8:37 am
Should be enough time.
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
April 28, 2009 at 8:42 am
April 28, 2009 at 7:19 pm
GilaMonster (4/28/2009)
Should be enough time.
That would be my gut feel too, but no way to tell. With lots of NC index corruption or a really crappy IO subsystem, or an IO subsystem that has to do read-retry for the majority of pages, it could end up taking longer than 8 hours. Could also be a single-cpu machine with a tiny tempdb that needs to autogrow. That's why I posted the link... it really depends 🙂
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
April 28, 2009 at 7:20 pm
Btw - you've got corruption in your database and you may be looking at data loss. Why are you waiting for a maintenance window to run CHECKDB? You need to run it ASAP to determine the extent of the damage to your database before it gets worse.
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
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply