November 25, 2010 at 3:50 am
The new database was created last night but DBCC is resulting in errors ...
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:671304) with latch type SH. 38(error not found) failed.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 14 pages from (1:671304) to (1:679391). See other errors for cause.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:679392) with latch type SH. 38(error not found) failed.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 14 pages from (1:679392) to (1:687479). See other errors for cause.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:687480) with latch type SH. 38(error not found) failed.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 14 pages from (1:687480) to (1:695567). See other errors for cause.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:695568) with latch type SH. 38(error not found) failed.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 14 pages from (1:695568) to (1:703655). See other errors for cause.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:703656) with latch type SH. 38(error not found) failed.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 14 pages from (1:703656) to (1:711743). See other errors for cause.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:711744) with latch type SH. 38(error not found) failed.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 14 pages from (1:711744) to (1:719831). See other errors for cause.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:719832) with latch type SH. 38(error not found) failed.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 14 pages from (1:719832) to (1:727919). See other errors for cause.
CHECKDB found 14 allocation errors and 0 consistency errors not associated with any single object.
CHECKDB found 14 allocation errors and 0 consistency errors in database 'mdc70_10'.
also backup is failing with error
Executing the query "BACKUP DATABASE [mdc70_10] TO DISK = N'L:\\Backup\\mdc70_10\\mdc70_10_backup_201011242103.bak' WITH RETAINDAYS = 2, NOFORMAT, NOINIT, NAME = N'mdc70_10_backup_20101124210312', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error: "A nonrecoverable I/O error occurred on file "G:\\Data\\mdc70_10.mdf:" 38(error not found).
BACKUP DATABASE is terminating abnormally.
10 percent processed.
20 percent processed.
30 percent processed.
40 percent processed.
50 percent processed.
60 percent processed.
70 percent processed.
80 percent processed.
90 percent processed.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Any input please?
Thanks
November 25, 2010 at 4:06 am
You've got some very severe, irreparable errors in this database. Restore from your last good backup.
Also do some checks of the IO subsystem on this machine. Something caused a lot of damage.
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
November 28, 2010 at 1:37 am
Thanks Gail.
I could restore the database from the backup.
Could you tell me how can I check for the I/O errors?
November 28, 2010 at 5:58 am
You check through the RAID logs, SAN logs (whichever is applicable), application logs, system logs and look for anything that looks like an IO error. You ask your system admins (or storage admins if its a SAN) to run appropriate diagnostics for whatever the IO subsystem is.
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
November 28, 2010 at 10:39 am
The IO errors are hardware or driver issues, in all likelihood, so follow Gail's advice and make sure someone does full diagnostics as re-using this hardware as is will likely result in more issues.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply