dbcc checktable with repair_allow_data_loss failed - please help!
-
Server: Msg 601, Level 12, State 3, Line 1
Could not continue scan with NOLOCK due to data movement.
Server: Msg 601, Level 12, State 1, Line 1
Could not continue scan with NOLOCK due to data movement.
Server: Msg 823, Level 24, State 2, Line 3
I/O error (bad page ID) detected during read at offset 0x000034d16d0000 in file 'K:\FOEDATA2\FOEDATA2.ndf'.
The statement has been terminated.
The statement has been terminated.
Connection Broken
-
What Transaction Isolation Level are you using?
I found this on Microsoft Support:
http://support.microsoft.com/default.aspx/kb/815008
Also what service pack is installed on your instance?
I found this article about a situation similar to yours, which was due to a bug fixed in SP3.
Hope this helps.
“If you're not outraged at the media, you haven't been paying attention.”
-
i using DBCC CHECKTABLE('Tablename', REPAIR_ALLOW_DATA_LOSS),it occured this following error message.
i install SP3 and hotfix (SQL2000-KB892059-v8.00.1007-x86-ENU.exe)
-
I'd start finding your backups. IO Errors in SQL Server are never nice thing and difficult to repair. Restoring from a backup is your best bet at getting a complete working database back.
If your running RAID, make sure that all your disks are ok, and that the controller hasn't reported any issues.
Julian Kuiters
juliankuiters.id.au -
PIggy-backing on Julian. Error 823 usually indicates hardware problems. The usual advise here is to check hardware and restore from the last good known backup
http://support.microsoft.com/default.aspx?scid=kb;en-us;828339
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply