January 2, 2013 at 4:05 am
--Error Number 824
DESCRIPTION:SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:845407; actual 1:607839). It occurred during a read of page (1:845407) in database ID 46 at offset 0x0000019ccbe000 in file ‘xx.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.
--If run this , I am getting below specified error message
DBCC CHECKDB ('DBname') WITH NO_INFOMSGS, ALL_ERRORMSGS
--Error message:
Msg 8946, Level 16, State 12, Line 1
Table error: Allocation page (1:145584) has invalid PFS_PAGE page header values. Type is 0. Check type, alloc unit ID and page ID on the page.
Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 6 pages from (1:145584) to (1:153671). See other errors for cause.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594050707456 (type Unknown), page (1:145584). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916617 and -4.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594050707456 (type Unknown), page (1:145584). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 62916617 and -4.
Can you suggest me to resolve this please….
Can you please let me know if you need any other details….
Thank you in Advance…..
Krishna
January 2, 2013 at 5:11 am
Please post the full and complete, unedited output of that command (you've left out at least one line, possibly more)
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
January 2, 2013 at 5:26 am
You are right. Thank you. I miss two lines ..Here is the complete error message...Please let me know if you need any other details........
Msg 8946, Level 16, State 12, Line 1
Table error: Allocation page (1:145584) has invalid PFS_PAGE page header values. Type is 0. Check type, alloc unit ID and page ID on the page.
Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 46 pages from (1:145584) to (1:153671). See other errors for cause.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594050707456 (type Unknown), page ID (1:145584) contains an incorrect page ID in its page header. The PageId in the page header = (1:70728).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594050707456 (type Unknown), page ID (1:145584) contains an incorrect page ID in its page header. The PageId in the page header = (1:70728).
CHECKDB found 2 allocation errors and 1 consistency errors not associated with any single object.
CHECKDB found 2 allocation errors and 1 consistency errors in database 'WSS_Content_HeartyLivesV2'.
Thank you,
Krishna
January 2, 2013 at 5:26 am
You are right. Thank you. I miss two lines ..Here is the complete error message...Please let me know if you need any other details........
Msg 8946, Level 16, State 12, Line 1
Table error: Allocation page (1:145584) has invalid PFS_PAGE page header values. Type is 0. Check type, alloc unit ID and page ID on the page.
Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 8998, Level 16, State 2, Line 1
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 46 pages from (1:145584) to (1:153671). See other errors for cause.
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594050707456 (type Unknown), page ID (1:145584) contains an incorrect page ID in its page header. The PageId in the page header = (1:70728).
Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 72057594050707456 (type Unknown), page ID (1:145584) contains an incorrect page ID in its page header. The PageId in the page header = (1:70728).
CHECKDB found 2 allocation errors and 1 consistency errors not associated with any single object.
CHECKDB found 2 allocation errors and 1 consistency errors in database 'WSS_Content_HeartyLivesV2'.
Thank you,
Krishna
January 2, 2013 at 6:27 am
Restore from a clean backup, that's not repairable in any way.
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
January 3, 2013 at 3:29 am
Hi Gail Shaw,
I did restore from healthy backup and it's fine now...Thank you
--Krishna
January 10, 2013 at 10:11 pm
This was removed by the editor as SPAM
January 11, 2013 at 3:03 am
Thank you very much ...
--Krishna
May 15, 2014 at 4:06 am
Try and run this
DBCC CHECKDB (Database name) WITH NO_INFOMSGS, ALL_ERRORMSGS
SSMS Expert
May 15, 2014 at 4:18 am
Please note: year old solved thread.
He did run that exact command, the results are in the third post in this very thread. If you insist on bumping every single corruption-related thread to advertise that recovery tool, please at least post something relevant, useful and correct.
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
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply