August 27, 2008 at 8:01 am
We are getting this error from the backup exec DB.
SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:599; actual 0:0). It occurred during a read of page (1:599) in database ID 4 at offset 0x000000004ae000 in file 'D:\BackupExec\MSSQL.5\MSSQL\DATA\MSDBData.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe 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.
I ran a dbcc checkdb and there were no errors returned.
Do I need to step it up a notch and run repair_rebuild? If I do how do I get BE into single_user mode?
I tried getting it into single mode and got an error about it still being used.
Thank you in advance.
Quinn
August 27, 2008 at 8:56 am
Is there actually a backup exec database or is it using the MSDB database. It appears from your error that it is MSDB. Are you seeing the error consistently? Odd that DBCC didn't return anything if there is more than one error.
I would not do the repair option at this point unless you are sure you are having problems.
Do you have backups? You might want to start checking into that too. Hopefully that will not be necessary.
Let me know what you are seeing regarding the errors and the actual database. Thanks.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
August 27, 2008 at 9:17 am
David,
Here is the error I am getting right out of the log file:
2008-08-15 04:00:02.45 spid55 SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x11b638c1; actual: 0x111a3bcf). It occurred during a read of page (1:598) in database ID 4 at offset 0x000000004ac000 in file 'D:\BackupExec\MSSQL.5\MSSQL\DATA\MSDBData.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe 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.
The database is SQLServer 2005 express.
Thanks
Quinn
August 27, 2008 at 9:27 am
This is definitely the MSDB database on your Express instance.
Please post the output of DBCC CHECKDB (msdb) WITH ALL_ERRORMSGS, NO_INFOMSGS so we can see what's wrong. Don't run repair as you may lose data. Do you have backups of msdb?
Thanks
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
August 27, 2008 at 9:31 am
I am not to familiar with Express so, there are probably others that can help more in this area. Have you had any other disk related errors or any IO related errors in the application or system log of the box this is running on. That would be a good thing to keep an eye on.
I had asked earlier if you had more than one occurrence of this error, can you supply that information?
Ultimately, if you run the repair you are going to risk some data loss potentially. If you are not seeing errors with checkdb and you are not seeing any more errors in the log then I would let it ride but start looking at the disks and the IO subsystem. I would also look to see what I had in backups prior to the error taking place and start to consider what data might be lost if you need to restore.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
August 27, 2008 at 9:34 am
Thanks Paul
Here is the output from that:
Msg 8906, Level 16, State 1, Line 1
Page (1:599) in database ID 4 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:600) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:601) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).
CHECKDB found 1 allocation errors and 2 consistency errors not associated with any single object.
Msg 8928, Level 16, State 1, Line 1
Object ID 1858105660, index ID 1, partition ID 72057594042777600, alloc unit ID 72057594047168512 (type In-row data): Page (1:598) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1858105660, index ID 1, partition ID 72057594042777600, alloc unit ID 72057594047168512 (type In-row data), page (1:598). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1858105660, index ID 1, partition ID 72057594042777600, alloc unit ID 72057594047168512 (type In-row data). Page (1:598) was not seen in the scan although its parent (1:597) and previous (1:549) refer to it. Check any previous errors.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'backupmediaset' (object ID 1858105660).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:4) identified by (media_set_id = 54 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '0B4CD456-0000-0000-0000-000000000000' and media_set_id = 54 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:5) identified by (media_set_id = 55 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '72F949BD-0000-0000-0000-000000000000' and media_set_id = 55 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:6) identified by (media_set_id = 56 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = 'DE318062-0000-0000-0000-000000000000' and media_set_id = 56 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:7) identified by (media_set_id = 57 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = 'EB6F062C-0000-0000-0000-000000000000' and media_set_id = 57 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:8) identified by (media_set_id = 58 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '62525803-0000-0000-0000-000000000000' and media_set_id = 58 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:9) identified by (media_set_id = 59 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '8735C9D7-0000-0000-0000-000000000000' and media_set_id = 59 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:10) identified by (media_set_id = 60 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '3FADC12A-0000-0000-0000-000000000000' and media_set_id = 60 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:11) identified by (media_set_id = 61 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '3A57DFA4-0000-0000-0000-000000000000' and media_set_id = 61 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:12) identified by (media_set_id = 62 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = 'AF35B17B-0000-0000-0000-000000000000' and media_set_id = 62 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:13) identified by (media_set_id = 63 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '76542608-0000-0000-0000-000000000000' and media_set_id = 63 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:14) identified by (media_set_id = 64 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '1514D223-0000-0000-0000-000000000000' and media_set_id = 64 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:15) identified by (media_set_id = 65 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = 'C295407E-0000-0000-0000-000000000000' and media_set_id = 65 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:16) identified by (media_set_id = 66 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '82D0D920-0000-0000-0000-000000000000' and media_set_id = 66 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:17) identified by (media_set_id = 67 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '716ADE2D-0000-0000-0000-000000000000' and media_set_id = 67 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:18) identified by (media_set_id = 68 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = 'E1ABDFEA-0000-0000-0000-000000000000' and media_set_id = 68 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:19) identified by (media_set_id = 69 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = 'FE2A4EA8-0000-0000-0000-000000000000' and media_set_id = 69 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:20) identified by (media_set_id = 70 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '89F3E3D2-0000-0000-0000-000000000000' and media_set_id = 70 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:21) identified by (media_set_id = 71 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = 'B81AB8B2-0000-0000-0000-000000000000' and media_set_id = 71 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:22) identified by (media_set_id = 72 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = 'AC5B3000-0000-0000-0000-000000000000' and media_set_id = 72 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:23) identified by (media_set_id = 73 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = 'C0162FAB-0000-0000-0000-000000000000' and media_set_id = 73 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:24) identified by (media_set_id = 74 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '1B86F913-0000-0000-0000-000000000000' and media_set_id = 74 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:25) identified by (media_set_id = 75 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '88156761-0000-0000-0000-000000000000' and media_set_id = 75 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:26) identified by (media_set_id = 76 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '1DFA8F84-0000-0000-0000-000000000000' and media_set_id = 76 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:27) identified by (media_set_id = 77 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '76B7DE3D-0000-0000-0000-000000000000' and media_set_id = 77 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:28) identified by (media_set_id = 78 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = 'BFAA1578-0000-0000-0000-000000000000' and media_set_id = 78 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:29) identified by (media_set_id = 79 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = 'C3105B2A-0000-0000-0000-000000000000' and media_set_id = 79 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:30) identified by (media_set_id = 80 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = 'AA968373-0000-0000-0000-000000000000' and media_set_id = 80 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:31) identified by (media_set_id = 81 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '7B469216-0000-0000-0000-000000000000' and media_set_id = 81 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:32) identified by (media_set_id = 82 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '5FB69495-0000-0000-0000-000000000000' and media_set_id = 82 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:33) identified by (media_set_id = 83 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '27FC757A-0000-0000-0000-000000000000' and media_set_id = 83 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:34) identified by (media_set_id = 84 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '200C4849-0000-0000-0000-000000000000' and media_set_id = 84 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:35) identified by (media_set_id = 85 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '20F2F17B-0000-0000-0000-000000000000' and media_set_id = 85 and family_sequence_number = 1 and mirror = 0).
Msg 8951, Level 16, State 1, Line 1
Table error: Table 'backupmediafamily' (ID 1890105774). Data row does not have a matching index row in index 'backupmediafamilyuuid' (ID 2). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:591:36) identified by (media_set_id = 86 and family_sequence_number = 1 and mirror = 0) with index values (media_family_id = '4C0D3E8B-0000-0000-0000-000000000000' and media_set_id = 86 and family_sequence_number = 1 and mirror = 0).
CHECKDB found 0 allocation errors and 33 consistency errors in table 'backupmediafamily' (object ID 1890105774).
Msg 8906, Level 16, State 1, Line 1
Page (1:594) in database ID 4 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 0_PCT_FULL'.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data). Page (1:594) was not seen in the scan although its parent (1:583) and previous (1:589) refer to it. Check any previous errors.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data). Index node page (1:583), slot 5 refers to child page (1:599) and previous child (1:594), but they were not encountered.
CHECKDB found 1 allocation errors and 2 consistency errors in table 'backupset' (object ID 1954106002).
Msg 8928, Level 16, State 1, Line 1
Object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data): Page (1:600) could not be processed. See other errors for details.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data). Page (1:600) was not seen in the scan although its parent (1:581) and previous (1:593) refer to it. Check any previous errors.
Msg 8928, Level 16, State 1, Line 1
Object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data): Page (1:601) could not be processed. See other errors for details.
Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data). Index node page (1:581), slot 8 refers to child page (1:601) and previous child (1:600), but they were not encountered.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'backupfile' (object ID 2050106344).
CHECKDB found 2 allocation errors and 44 consistency errors in database 'msdb'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (msdb).
Thanks
Quinn
August 27, 2008 at 9:44 am
This feels to me that something stomped on an extent's worth of pages starting at 1:598 in msdb. I'd follow David's advice around checking out your IO subsystem. You could run repair and it looks like you'll lose a bunch of backup history or you could restore/rebuild msdb. If you choose that route, see my old blog post http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/06/619304.aspx
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
August 27, 2008 at 10:38 am
Paul
That is interesting information. Thanks for the link.
Quinn
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply