April 7, 2010 at 6:41 am
I am getting the following error on some of the databases recently. From last 3 days this error is reported every day by some programmers. Initially i restored the one of the databse but i am gettiing this for others too, what is the problem causing this and the possible solution.
Error:
Msg 824, Level 24, State 2, Line 1
SQL Server detected a logical consistency-based I/O error:
incorrect pageid (expected 1:5276956; actual 0:496).
It occurred during a read of page (1:5276956) in database ID 16 at offset 0x00000a10a38000 in file
'F:\xxx\xxx_data.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.
April 7, 2010 at 6:45 am
some of the pages of ur databases are corrupt. Do you have a clean backup from where u can restore the database?
April 7, 2010 at 7:08 am
yes we do but any idea why is this occuring all of a sudden only on that server, can i blame the disk drive for it or any thing that can be done from sql server ?
April 7, 2010 at 7:18 am
Is it a RAID? Have you checked each disk's health?
April 7, 2010 at 7:27 am
it is not RAID, as that is a test server, we are managing with local disks.
April 7, 2010 at 8:29 am
I did run DBCC CHECKDB ('Stg_Budget') WITH NO_INFOMSGS and got the following....
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 334624235, index ID 0, partition ID 72057594051166208, alloc unit ID 72057594087735296 (type In-row data), page ID (1:242412) contains an incorrect page ID in its page header. The PageId in the page header = (1:242428).
Msg 8928, Level 16, State 1, Line 1
Object ID 334624235, index ID 0, partition ID 72057594051166208, alloc unit ID 72057594087735296 (type In-row data): Page (1:242412) could not be processed. See other errors for details.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 334624235, index ID 0, partition ID 72057594051166208, alloc unit ID 72057594087735296 (type In-row data), page ID (1:251103) contains an incorrect page ID in its page header. The PageId in the page header = (1:251063).
Msg 8928, Level 16, State 1, Line 1
Object ID 334624235, index ID 0, partition ID 72057594051166208, alloc unit ID 72057594087735296 (type In-row data): Page (1:251103) could not be processed. See other errors for details.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 334624235, index ID 0, partition ID 72057594051166208, alloc unit ID 72057594087735296 (type In-row data), page ID (1:665287) contains an incorrect page ID in its page header. The PageId in the page header = (1:665271).
Msg 8928, Level 16, State 1, Line 1
Object ID 334624235, index ID 0, partition ID 72057594051166208, alloc unit ID 72057594087735296 (type In-row data): Page (1:665287) could not be processed. See other errors for details.
Msg 8928, Level 16, State 1, Line 1
Object ID 334624235, index ID 0, partition ID 72057594051166208, alloc unit ID 72057594087735296 (type In-row data): Page (1:665865) could not be processed. See other errors for details.
Msg 8944, Level 16, State 12, Line 1
Table error: Object ID 334624235, index ID 0, partition ID 72057594051166208, alloc unit ID 72057594087735296 (type In-row data), page (1:665865), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 41 and 17.
Msg 8944, Level 16, State 12, Line 1
Table error: Object ID 334624235, index ID 0, partition ID 72057594051166208, alloc unit ID 72057594087735296 (type In-row data), page (1:665865), row 0. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 41 and 17.
CHECKDB found 0 allocation errors and 9 consistency errors in table 'BudgetFeed' (object ID 334624235).
CHECKDB found 0 allocation errors and 9 consistency errors in database 'Stg_Budget'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Stg_Budget).
April 7, 2010 at 8:35 am
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB
You will lose data from the corrupted pages. If you're okay with data loss you can perform dbcc checkdb with repair_allow_data_loss option. OR restore from a past clean backup.
April 7, 2010 at 10:38 am
^^Yes what you suggest. Best to restore from the last backup. Looks like you will have data loss going with DBCC repair process.
April 7, 2010 at 2:43 pm
Depending on the recovery model and DR strategy, you can also restore only the pages you are concerned with...
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply