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

Msg 824, Level 24, State 2, Line 1 SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:16514; actual 0:0). It occurred... Expand / Collapse
Author
Message
Posted Wednesday, August 20, 2014 3:51 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, August 20, 2014 10:12 PM
Points: 2, Visits: 5
im getting this error while executing

"DBCC CheckDB('test') WITH NO_INFOMSGS, ALL_ERRORMSGS, TABLOCK"

Msg 824, Level 24, State 2, Line 1 SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:16514; actual 0:0). It occurred during a read of page (1:16514) in database ID 8 at offset 0x00000008104000 in file 'G:\test\test.mdf'. Additional messages in the SQL Server
please help me out with dis problem the database is in emergency mode. it is not getting recovered
Post #1605349
Posted Wednesday, August 20, 2014 4:33 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Today @ 5:37 AM
Points: 269, Visits: 360
anoosha.konaparthi (8/20/2014)
im getting this error while executing

"DBCC CheckDB('test') WITH NO_INFOMSGS, ALL_ERRORMSGS, TABLOCK"

Msg 824, Level 24, State 2, Line 1 SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:16514; actual 0:0). It occurred during a read of page (1:16514) in database ID 8 at offset 0x00000008104000 in file 'G:\test\test.mdf'. Additional messages in the SQL Server
please help me out with dis problem the database is in emergency mode. it is not getting recovered


use below link :
http://www.experts-exchange.com/Software/Server_Software/Microsoft_Server_Applications/Q_27646266.html

and

http://www.sqlservercentral.com/Forums/Topic522169-266-1.aspx



Vimal Lohani
SQL DBA | MCP (70-461,70-462)

==============================
The greatest barrier to success is the fear of failure
** Success is a journey not a destination
**

Think before you print, SAVE TREES, Protect Mother Nature
Post #1605354
Posted Wednesday, August 20, 2014 5:48 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 2:13 PM
Points: 39,866, Visits: 36,208
Please post the full and complete, unedited output of that CheckDB command.

DO NOT do anything else at this point. Please note that the advice given in the thread linked above may not be relevant in your case. Do not follow it



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 #1605378
Posted Wednesday, August 20, 2014 9:10 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, August 20, 2014 9:05 PM
Points: 1, Visits: 0
Your database test.mdf is corrupt. If you have a backup, then just restore with that backup. If you don't, then you may use REPAIR_REBUILD or REPAIR_ALLOW_DATA_LOSS parameters in DBCC CHeckdb to try to fix the corruption. Note you must make a backup of your current Test.mdf before calling these parameters.

There are also some online resources discussing about this situation, for example:

http://www.datanumen.com/sql-recovery/problems/checkdb-checktable-fail.htm

Good luck!
Post #1605648
Posted Wednesday, August 20, 2014 10:13 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, August 20, 2014 10:12 PM
Points: 2, Visits: 5
Again getting the same error after executing the above
Post #1605652
Posted Wednesday, August 20, 2014 10:35 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 2:46 PM
Points: 1,902, Visits: 5,235
anoosha.konaparthi (8/20/2014)
Again getting the same error after executing the above


Repeating Gail's request:
Please post the full and complete, unedited output of that CheckDB command. DO NOTHING ELSE FOR NOW!

If you don't know exactly what is wrong, how are you going to fix it?
Post #1605655
Posted Thursday, August 21, 2014 12:49 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 2:13 PM
Points: 39,866, Visits: 36,208
copper_sunflower (8/20/2014)
If you don't, then you may use REPAIR_REBUILD or REPAIR_ALLOW_DATA_LOSS parameters in DBCC CHeckdb to try to fix the corruption.


No, please no. We don't yet know exactly what's wrong, posting any kind of fix when we don't know the actual damage is irresponsible.



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 #1605678
Posted Thursday, August 21, 2014 12:51 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 2:13 PM
Points: 39,866, Visits: 36,208
anoosha.konaparthi (8/20/2014)
Again getting the same error after executing the above


Please run just the following, post the full and complete, unedited output and I'll be able to give you useful advice. Without that we're guessing and people's guesses may easily make matters worse.

DBCC CheckDB (<database name>) WITH NO_INFOMSGS, ALL_ERRORMSGS




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 #1605679
Posted Monday, September 8, 2014 7:01 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, September 8, 2014 7:00 AM
Points: 25, Visits: 41
As the main reason of SQL error 823 is page level corruption. Basically SQL Server performs its I/O operation through API if he finds check fails then immediately it reports an error. So I recommend you to check the hardware first.

SSMS Expert
Post #1611422
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse