SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 I/O error
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

milapi65
Starting Member

2 Posts

Posted - 10/28/2010 :  07:52:52  Show Profile  Reply with Quote
Hi,

We have a customer which we tried to help with a sql database problem. Currently the backup is not running due to error 1117 - I/O error. We dettached the database and tried to make a copy - this is also not possible due to I/O error (Windows Server 2003). The application which uses the database is still activate and running ok.
We run a dbcc checkdb on the database which results in following errors.
Any advice how to fix the problem is appreciated.

Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:559032) with latch type SH. 1117(The request could not be performed because of an I/O device error.) failed.
Msg 8966, Level 16, State 2, Line 1
Unable to read and latch page (1:559033) with latch type SH. 1117(The request could not be performed because of an I/O device error.) failed.
CHECKDB found 0 allocation errors and 2 consistency errors not associated with any single object.
--------------------------------------------
Object ID 114099447, index ID 1, partition ID 72057594070237184, alloc unit ID 72057594072596480 (type In-row data): Errors found in off-row data with ID 51138461696 owned by data record identified by RID = (1:558745:15)
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:559032) allocated to object ID 114099447, index ID 1, partition ID 72057594070237184, alloc unit ID 72057594072727552 (type LOB data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 114099447, index ID 1, partition ID 72057594070237184, alloc unit ID 72057594072727552 (type LOB data). The off-row data node at page (1:559032), slot 0, text ID 51138461696 is referenced by page (1:558787), slot 0, but was not seen in the scan.
Msg 2533, Level 16, State 1, Line 1
Table error: page (1:559033) allocated to object ID 114099447, index ID 1, partition ID 72057594070237184, alloc unit ID 72057594072727552 (type LOB data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.
Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 114099447, index ID 1, partition ID 72057594070237184, alloc unit ID 72057594072727552 (type LOB data). The off-row data node at page (1:559033), slot 0, text ID 51138461696 is referenced by page (1:558787), slot 0, but was not seen in the scan.
-----------------------------------------------

russell
Pyro-ma-ni-yak

USA
5072 Posts

Posted - 10/28/2010 :  10:36:17  Show Profile  Visit russell's Homepage  Reply with Quote
the table with object_id 114099447 is corrupt. you've lost some LOBs it seems.

you do have backups right?

need to repair i/o subsystem 1st. failed disk(s) possibly. or controller.

never, never, never detach a database when there is corruption or disk errors -- u may not be able to attach it later.
Go to Top of Page

milapi65
Starting Member

2 Posts

Posted - 10/28/2010 :  10:59:32  Show Profile  Reply with Quote
Thanks your prompt reply. They only have older backups, but since the database contains email correspondence they don't want to go back loosing actual emails.

Strange enough, they informed us, that the harddisk where the database is stored is an external USB device.

Since we are not able to copy the database to another disk, shall we try executing chkdsk to repair the filesystem?

Tonight we are going to try exporting data from the corrupt table to another disk to see how much data we can get.

Thanks.
Go to Top of Page

GilaMonster
Flowing Fount of Yak Knowledge

South Africa
4507 Posts

Posted - 10/28/2010 :  11:17:50  Show Profile  Visit GilaMonster's Homepage  Reply with Quote
That checkDB output is not complete. Please run the following and post the full and complete output.

DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

First things first - take a full backup. Yes, it'll be damaged, but it's better than nothing.

Database on a non-redundant USB drive? I'd say this is getting what they asked for. USB has write limitations and is NOT designed for prolonged constant read/write that a SQL database will do.

--
Gail Shaw
SQL Server MVP
Go to Top of Page

russell
Pyro-ma-ni-yak

USA
5072 Posts

Posted - 10/28/2010 :  12:35:16  Show Profile  Visit russell's Homepage  Reply with Quote
quote:
Originally posted by GilaMonster

Database on a non-redundant USB drive? I'd say this is getting what they asked for.


lol
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.23 seconds. Powered By: Snitz Forums 2000