July 21, 2017 at 12:13 pm
Hi guys,
Well here is my story, when I tried to get data from a specific table from my DB it showed me this error:
Msg 823, Level 24, State 2, Line 2
The operating system returned error 23(Erro nos dados (verificação cíclica de redundância).) to SQL Server during a read at offset 0x0000000742a000 in file 'C:\ProgramData\Voith Hydro\HyCon MD\data\MODI_RT_SA_1.7.0.NDF'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level 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.
Then, when I checked my DB using DBCC CHECKDB this error came out:
Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'MODI_RT_DATA'.
I hope someone could help me with this. I want to find the cause of this and of course get a solution.
Regards.
Hermi.
July 21, 2017 at 1:48 pm
The 823 error indicates that SQL Server requested a page from Windows and Windows could not return the page. Do you see any additional information in the SQL Server error log?
For the DBCC CHECKDB error, check the tempdb database for space issues.
July 21, 2017 at 2:24 pm
If CheckDB's returning that, it's probably a fatal error.
Do you have a clean backup of this 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
July 21, 2017 at 2:53 pm
Might not hurt to run chkdsk on the drive as well. Could be the disk is starting to fail.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
July 26, 2017 at 8:47 am
skreebydba - Friday, July 21, 2017 1:48 PMThe 823 error indicates that SQL Server requested a page from Windows and Windows could not return the page. Do you see any additional information in the SQL Server error log?
For the DBCC CHECKDB error, check the tempdb database for space issues.
Hi! Thank you for answer.
This is what I got from cheking the tempdb database. I´m not sure if this is ok.
July 26, 2017 at 8:55 am
GilaMonster - Friday, July 21, 2017 2:24 PMIf CheckDB's returning that, it's probably a fatal error.Do you have a clean backup of this database?
Thanks for answering!
Yes, I have a clean backup, how should I use this backup?. I don´t want to make any fatal mistake in my database. Do you have any link where I can find how to do this correctly?
July 26, 2017 at 9:05 am
bmg002 - Friday, July 21, 2017 2:53 PMMight not hurt to run chkdsk on the drive as well. Could be the disk is starting to fail.
Hi!! Thanks for you answer.
I checked the hard drive, it seems to be good. But, I still doubt from the hard drive because the computer feels really slow.
July 26, 2017 at 12:56 pm
palasatenea_hermi - Wednesday, July 26, 2017 8:55 AMGilaMonster - Friday, July 21, 2017 2:24 PMIf CheckDB's returning that, it's probably a fatal error.Do you have a clean backup of this database?
Thanks for answering!
Yes, I have a clean backup, how should I use this backup?.
Restore it. The DB's most likely toast, so restore from backup, apply log backups to get back up to date.
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
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply