August 19, 2009 at 3:41 am
This is my first post on this forum and the problem that i m facing is that while accesing data from SQL through Visual basic application the system is givin the following error
Runtime error-2147467259(80004005)
I/O error(torn Page) detected during read at offset 0x00000003efe000 in file C:\Programe Files\MS SQL Server\MSSQL\data\*****.mdf
I m new to all this SQL thing so could anyone pls help me on this will be really appericiated. Thanks in advance.
August 19, 2009 at 8:20 am
Ouch, your database has inconsistency errors and you'll more than likely find that some of your data is corrupt. Have you got backups of the DB that you can restore?
August 19, 2009 at 8:25 am
Before you do anything else to this database.
1) Please run this and post the full output
DBCC CHECKDB (< Database Name > ) WITH NO_INFOMSGS, ALL_ERRORMSGS
2) Take a look at this article. http://www.sqlservercentral.com/articles/65804/
Do you have a clean backup of this database?
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
August 19, 2009 at 11:18 pm
Thanks for the replies mates. I run the DBCC and the result is as follows
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:12877). The PageId in the page header = (0:0).
Server: Msg 8909, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page ID (1:12878). The PageId in the page header = (0:0).
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1080963523, index ID 0: Page (1:8063) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1080963523, index ID 0, page (1:8063). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1080963523, index ID 1. Page (1:7929) is missing a reference from previous page (1:8063). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1080963523, index ID 1. Page (1:8063) was not seen in the scan although its parent (1:640) and previous (1:1739) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1746013897, index ID 0: Page (1:12877) could not be processed. See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1746013897, index ID 0: Page (1:12878) could not be processed. See other errors for details.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1746013897, index ID 1. Page (1:10059) is missing a reference from previous page (1:12878). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1746013897, index ID 1. Page (1:12556) is missing a reference from previous page (1:12877). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1746013897, index ID 1. Page (1:12877) was not seen in the scan although its parent (1:11745) and previous (1:12876) refer to it. Check any previous errors.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1746013897, index ID 1. Page (1:12878) was not seen in the scan although its parent (1:11745) and previous (1:12556) refer to it. Check any previous errors.
CHECKDB found 0 allocation errors and 2 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 4 consistency errors in table 'btentry' (object ID 1080963523).
CHECKDB found 0 allocation errors and 6 consistency errors in table 'SUBTREChallan' (object ID 1746013897).
CHECKDB found 0 allocation errors and 12 consistency errors in database 'treasury2008_09'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (treasury2008_09 ).
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply