I/O error (bad page ID)...

Question

I/O error (bad page ID)...

lartrond

SSC Veteran

Points: 237
More actions
November 9, 2004 at 5:04 am

#87027

In one of my tables I get this error message when I open the table thru the program that uses sql server:
select UpdVo.* from Updvo where (UpdVo.DbAcNo = 2410) order by.......
If I the try to run this statement thru query analyser I get this statement:
Server: Msg 823, Level 24, State 2, Line 1
I/O error (bad page ID) detected during read at offset 0x00000002c8e000 in file 'C:\xxx\F0001_Data.mdf'.
Connection Broken
I tried to copy the table out to a flat text file but enterprise manager returns with the same message but specifies that: Error at Source for Row number 14334. Errors encountered so far in this task: 1.
The problem is that I can't find in UpdVo tabel any records of 2410 in DbAcNo
What can I do to correct this ? And no, the customer who I work for now, don't have any backup

Viewing 6 posts - 1 through 5 (of 5 total)

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

Frank Kalis SSC Guru Points: 111183 More actions · Answer 1

Did you already try DBCC CHECKTABLE?

--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]

lartrond SSC Veteran Points: 237 More actions · Answer 2

Yes, and the statement I got back was:

Server: Msg 8909, Level 16, State 1, Line 1

Table error: Object ID 645, index ID 24392, page ID (1:5703). The PageId in the page header = (10378:135098).

Server: Msg 8928, Level 16, State 1, Line 1

Object ID 501680935, index ID 0: Page (1:5703) could not be processed. See other errors for details.

CHECKTABLE found 0 allocation errors and 1 consistency errors in table '(Object ID 645)' (object ID 645).

DBCC results for 'UpdVo'.

There are 18187 rows in 1654 pages for object 'UpdVo'.

CHECKTABLE found 0 allocation errors and 1 consistency errors in table 'UpdVo' (object ID 501680935).

Then I tried this statement after reading some more:

DBCC CHECKTABLE

( 'UpdVo' , REPAIR_ALLOW_DATA_LOSS )

With this result:

Server: Msg 7919, Level 16, State 3, Line 1

Repair statement not processed. Database needs to be in single user mode.

Trying now again with ALTER DATABASE xxxx SET SINGLE_USER first

Guus Kramer Ten Centuries Points: 1031 More actions · Answer 3

Hi,

This is an operating system, driver, or hardware problem which indicates a data integrity-related error. Your pages or IAMs are not in chaning order....

For more details see http://support.microsoft.com/default.aspx?scid=kb;en-us;826433

GKramer

The Netherlands.

MAK-150500 SSC Eights! Points: 869 More actions · Answer 4

When I've had these errors, they are always associated with bad disk sectors. Check your disk, and fix if necessary.

Frank Kalis SSC Guru Points: 111183 More actions · Answer 5

Sorry, got somehow lost of this thread.

The 823 error basically says, that this page cannot physically be read from disk. You should replace the disk and restore from the last good known backup.

--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]