August 26, 2013 at 2:06 am
I first ran DBCC CHECKDB on an instance. It threw away around 2000 consistency errors.
I ran repair_rebuild and it didn't fix any errors.
Then I ran dbcc with REPAIR_ALLOW_DATA_LOSS and it fixed around 1900 consistency errors.
I switched DB into multi user mode again and am running checkdb again.
is there a way I can fix the remaining 100 odd errors?
August 26, 2013 at 3:12 am
Firstly why did you repair rather than restoring a clean backup? Repair is typically the last resort, not the first solution.
Do you know how much data was lost?
Do you know what data was lost?
Do you know what effect that lost data will have on your business?
Please run the following and post the full and complete, unedited output.
DBCC CheckDB (<database name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
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
September 9, 2013 at 2:25 am
GilaMonster (8/26/2013)
Firstly why did you repair rather than restoring a clean backup? Repair is typically the last resort, not the first solution.Do you know how much data was lost?
Do you know what data was lost?
Do you know what effect that lost data will have on your business?
Please run the following and post the full and complete, unedited output.
DBCC CheckDB (<database name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
Hi,
Will be backup be clean without inconsistencies?
September 9, 2013 at 3:17 am
it depends if the backup has been taken before the corruption occured.
One way of testing this is using Allens automation script : Test Your SQL Server Backups with PowerShell[/url]
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
September 9, 2013 at 3:41 am
If corruption re-occurs, it is time to check your disks, .. double check if your case can be found in the BUGs of Service packs or Cumulative updates you didn't install at this instance and/or contact PSS.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
September 9, 2013 at 4:25 am
Benki Chendu (9/9/2013)
GilaMonster (8/26/2013)
Firstly why did you repair rather than restoring a clean backup? Repair is typically the last resort, not the first solution.Do you know how much data was lost?
Do you know what data was lost?
Do you know what effect that lost data will have on your business?
Please run the following and post the full and complete, unedited output.
DBCC CheckDB (<database name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
Hi,
Will be backup be clean without inconsistencies?
Well, I specified 'clean backup', so one without corruption in it.
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
September 9, 2013 at 8:33 am
I also see stack dumps getting generated.
Am planning to engage MS to decipher the stack dump.
Makes sense?
September 9, 2013 at 11:16 am
If you want to pay them, sure.
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
September 9, 2013 at 11:18 am
Not really.
I was almost clueless 😀
Can you please help me if you can
September 9, 2013 at 11:41 am
GilaMonster (8/26/2013)
Please run the following and post the full and complete, unedited output.
DBCC CheckDB (<database name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
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
September 10, 2013 at 1:07 am
Please Find the error messages attached
September 10, 2013 at 3:28 am
Restore from a clean backup (one taken before the corruption occurred).
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
September 10, 2013 at 3:30 am
Ok. Any major insights as such from the error messages
September 10, 2013 at 3:41 am
Yes, you've got some problems with your IO subsystem that's caused major, widespread corruption in your database.
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
September 10, 2013 at 3:43 am
oh ok. DB's are on SAN. I spoke to my SAN admin yesterday and he told me that he doesn't see any issues from SAN side. Typical answer from them most of the times:hehe::cool:
Viewing 15 posts - 1 through 15 (of 17 total)
You must be logged in to reply to this topic. Login to reply