SQL2K: Issue on DBCC CHECKDB - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

Data Corruption Issues

SQL2K: Issue on DBCC CHECKDB

Author

Topic

dewacorp.alliances

452 Posts

Posted - 2006-08-25 : 19:43:22

Hi there

When I run DBCC CHECKDB, I got the following error. I only pick which the one that have an error. Due to there is no good backup and I don't want to run DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS as yet cause the app still running ok at this stage, if I do detach the database and copy the MDF and LDF somewhere and do the re-attach back to second server, will it a good idea to cover this by doing the DBCC CHECKDB repair_allow_data_loss on the second server perhaps? My concern is if I detach back on the first server, will it be back to retach again on first server?

Thanks

===================================================

Server: Msg 8966, Level 16, State 2, Line 1
Could not read and latch page (1:1261) with latch type UP. 23(error not found) failed.
DBCC results for 'db01210101_2'.
CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.
DBCC results for 'sysobjects'.
There are 1438 rows in 24 pages for object 'sysobjects'.
DBCC results for 'CAT_TypesTexts'.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15553789952 owned by data record identified by RID = (1:1632:0) ScheduleHistoryID = 11632.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15579480064 owned by data record identified by RID = (1:3488:1) ScheduleHistoryID = 11711.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15605825536 owned by data record identified by RID = (1:3489:0) ScheduleHistoryID = 11808.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15678046208 owned by data record identified by RID = (1:3490:30) ScheduleHistoryID = 12078.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15678570496 owned by data record identified by RID = (1:3490:32) ScheduleHistoryID = 12080.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15680405504 owned by data record identified by RID = (1:3490:39) ScheduleHistoryID = 12087.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15680929792 owned by data record identified by RID = (1:3490:41) ScheduleHistoryID = 12089.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15682502656 owned by data record identified by RID = (1:3491:3) ScheduleHistoryID = 12095.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15682764800 owned by data record identified by RID = (1:3491:4) ScheduleHistoryID = 12096.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15683026944 owned by data record identified by RID = (1:3491:5) ScheduleHistoryID = 12097.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15684075520 owned by data record identified by RID = (1:3491:9) ScheduleHistoryID = 12101.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15685124096 owned by data record identified by RID = (1:3491:13) ScheduleHistoryID = 12105.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15685713920 owned by data record identified by RID = (1:3491:16) ScheduleHistoryID = 12108.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15685976064 owned by data record identified by RID = (1:3491:17) ScheduleHistoryID = 12109.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15687155712 owned by data record identified by RID = (1:3491:23) ScheduleHistoryID = 12115.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15689842688 owned by data record identified by RID = (1:3491:27) ScheduleHistoryID = 12119.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15691415552 owned by data record identified by RID = (1:3491:32) ScheduleHistoryID = 12124.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15693381632 owned by data record identified by RID = (1:3491:39) ScheduleHistoryID = 12131.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15696527360 owned by data record identified by RID = (1:3491:51) ScheduleHistoryID = 12143.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15697182720 owned by data record identified by RID = (1:3491:54) ScheduleHistoryID = 12146.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 693577509: Errors found in text ID 15700983808 owned by data record identified by RID = (1:3491:69) ScheduleHistoryID = 12161.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1261) allocated to object ID 693577509, index ID 255 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 0, text ID 15685713920 is referenced by page (1:3491), slot 16, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 1, text ID 15687155712 is referenced by page (1:3491), slot 23, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 2, text ID 15553789952 is referenced by page (1:1632), slot 0, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 3, text ID 15579480064 is referenced by page (1:3488), slot 1, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 4, text ID 15605825536 is referenced by page (1:3489), slot 0, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 5, text ID 15685976064 is referenced by page (1:3491), slot 17, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 6, text ID 15689842688 is referenced by page (1:3491), slot 27, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 7, text ID 15691415552 is referenced by page (1:3491), slot 32, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 8, text ID 15693381632 is referenced by page (1:3491), slot 39, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 9, text ID 15696527360 is referenced by page (1:3491), slot 51, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 10, text ID 15697182720 is referenced by page (1:3491), slot 54, but was not seen in the scan.
DBCC results for 'ScheduleHistory'.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 11, text ID 15700983808 is referenced by page (1:3491), slot 69, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 13, text ID 15678046208 is referenced by page (1:3490), slot 30, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 14, text ID 15678570496 is referenced by page (1:3490), slot 32, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 15, text ID 15680405504 is referenced by page (1:3490), slot 39, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 16, text ID 15680929792 is referenced by page (1:3490), slot 41, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 17, text ID 15682502656 is referenced by page (1:3491), slot 3, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 18, text ID 15682764800 is referenced by page (1:3491), slot 4, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 19, text ID 15683026944 is referenced by page (1:3491), slot 5, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 29, text ID 15684075520 is referenced by page (1:3491), slot 9, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 693577509. The text, ntext, or image node at page (1:1261), slot 30, text ID 15685124096 is referenced by page (1:3491), slot 13, but was not seen in the scan.
There are 5619 rows in 75 pages for object 'ScheduleHistory'.
CHECKDB found 0 allocation errors and 43 consistency errors in table 'ScheduleHistory' (object ID 693577509).

CHECKDB found 0 allocation errors and 44 consistency errors in database 'db01210101_2'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (db01210101_2 ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

dewacorp.alliances

452 Posts

Posted - 2006-08-27 : 00:41:27

Update:

Try the following:
1. Shutdown the MSSQL service and copy mdf and ldf and the result is unsuccessfull.
2. Run Check Disk and it's a complete. I thought this will recover and try do do a backup still the error comes which is: "Non recoverable I/O error occured on file xxx.mdf. Backup database is terminating abnormally."
3. Run DBCC CHECKDB REPAIR_ALLOW_DATA_LOSS and then REPAIR_FAST and it did fix and no consistency error any more. So I thought this will fixed ... so I run backup once again and it comes up the same error (2).

I am running out an option here. Any ideas?

Thanks

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2006-08-28 : 17:35:04

You've got a hard corruption on the disk. Backup is unable to read the page off disk and so cannot complete the backup. I recommend that you manually transfer all the data to a new database *on a different drive* and then get rid of the broken drive(s).

I'd also run CHECKDB on any other databases that are stored on those drives.

Paul Randal
Lead Program Manager, Microsoft SQL Server Core Storage Engine (Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)

dewacorp.alliances

452 Posts

Posted - 2006-08-29 : 01:44:36

quote:
Originally posted by paulrandal

You've got a hard corruption on the disk. Backup is unable to read the page off disk and so cannot complete the backup. I recommend that you manually transfer all the data to a new database *on a different drive* and then get rid of the broken drive(s).

Thanks for that. I check with CHKDSK and it said 0 for bad sector. Am I using the right utility to find out bad sector is?

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2006-08-29 : 07:49:37

quote:
Originally posted by valdyv

Thanks for that. I check with CHKDSK and it said 0 for bad sector. Am I using the right utility to find out bad sector is?

did you use the /R option for chkdsk?

do you have any disk related errors in your system event log?

-ec

dewacorp.alliances

452 Posts

Posted - 2006-09-01 : 00:16:12

I ran CHKDSK /R and reboot the box. The process seems marked the bad sector and the database is still up and recoved.

I am thinking to ghost this disk to different disk. Would it the bad sector get copied as well?

Thanks

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2006-09-05 : 17:29:54

Well, if the bad sector wsa remapped, the new sector won't have any of the original SQL data from the old sector in - so the database page will still be corrupt. What do you get if you run CHECKDB again?

Paul Randal
Lead Program Manager, Microsoft SQL Server Core Storage Engine (Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources