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

Question

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

anoosha.konaparthi

SSC Veteran

Points: 298
More actions
August 20, 2014 at 3:51 am

#298490

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

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Vimal Lohani SSCommitted Points: 1650 More actions · Answer 1

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 LohaniSQL 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

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 2

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, MVP, M.Sc (Comp Sci)
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

copper_sunflower Valued Member Points: 73 More actions · Answer 3

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!

anoosha.konaparthi SSC Veteran Points: 298 More actions · Answer 4

anoosha.konaparthi

SSC Veteran

Points: 298

August 20, 2014 at 10:13 pm

#1739759

Again getting the same error after executing the above

Eirikur Eiriksson SSC Guru Points: 182911 More actions · Answer 5

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?

😎

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 6

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, MVP, M.Sc (Comp Sci)
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

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 7

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, MVP, M.Sc (Comp Sci)
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

Elliswhite SSCommitted Points: 1783 More actions · Answer 8

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