Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server detected a logical consistency-based I/O error Expand / Collapse
Author
Message
Posted Wednesday, January 2, 2013 4:04 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 5:03 AM
Points: 169, Visits: 762
--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


Post #1401754
Posted Wednesday, January 2, 2013 5:11 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 2:48 AM
Points: 42,438, Visits: 35,493
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 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1401787
Posted Wednesday, January 2, 2013 5:26 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 5:03 AM
Points: 169, Visits: 762
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
Post #1401791
Posted Wednesday, January 2, 2013 5:26 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 5:03 AM
Points: 169, Visits: 762
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
Post #1401792
Posted Wednesday, January 2, 2013 6:27 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 2:48 AM
Points: 42,438, Visits: 35,493
Restore from a clean backup, that's not repairable in any way.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1401809
Posted Thursday, January 3, 2013 3:29 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 5:03 AM
Points: 169, Visits: 762
Hi Gail Shaw,

I did restore from healthy backup and it's fine now...Thank you

--Krishna
Post #1402269
Posted Thursday, January 10, 2013 10:11 PM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, July 16, 2014 5:10 AM
Points: 112, Visits: 1,207
Please check this article: http://support.microsoft.com/kb/2015756

SQL Database Recovery Expert
Post #1405755
Posted Friday, January 11, 2013 3:03 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 5:03 AM
Points: 169, Visits: 762
Thank you very much ...

--Krishna

Post #1405850
Posted Thursday, May 15, 2014 4:06 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, June 11, 2014 2:38 AM
Points: 21, Visits: 36
Try and run this

DBCC CHECKDB (Database name) WITH NO_INFOMSGS, ALL_ERRORMSGS


SSMS Expert
Post #1571215
Posted Thursday, May 15, 2014 4:18 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 2:48 AM
Points: 42,438, Visits: 35,493
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 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1571221
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse