Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

torn page error

Status
Not open for further replies.

Paulvtis

MIS
Aug 1, 2002
36
PH
this is the error:

[microsoft][ODBC sql server][sql server]I/O (torn page) detected during read at offset 0x00000000003c22000 in file 'c:\sqldata\ms......mdf'.

This prompted in our ERP software that is using SQL 2000 when I go to one of the modules. But generally the database is still working.

Please help if this can still be fixed or how?

Thanks a lot
 
The first thing that you need to do a run a DBCC CHECKDB on the database and see just how bad the corruption is. It will give you some output that will tell you the fix level that you will need to use to correct the problem.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
Below is the error after running checkdb can the db still be fixed?

Server: Msg 8928, Level 16, State 1, Line 1
Object ID 2, index ID 255: Page (1:7697) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 2, index ID 255, page (1:7697). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 12, index ID 0: Page (1:4389) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 12, index ID 0, page (1:4389). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.


DBCC results for 'UIGPI'.
DBCC results for 'sysobjects'.
There are 10009 rows in 155 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 2574 rows in 111 pages for object 'sysindexes'.
CHECKDB found 0 allocation errors and 2 consistency errors in table 'sysindexes' (object ID 2).
DBCC results for 'syscolumns'.
There are 71932 rows in 1128 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 9641 rows in 2949 pages for object 'syscomments'.
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.

etc....

....
....
....
 
on the lowest part this is what is written after checkdb:


CHECKDB found 0 allocation errors and 4 consistency errors in database 'UIGPI'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (UIGPI ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

How can the repair be executed?

Thanks .
 
Based on the error message the database can be fixed.
Code:
DBCC CHECKDB ('Database', REPAIR_ALLOW_DATA_LOSS)
You may loose data from the sysindexes and sysdepends tables. After you run this, you will want to make sure that all your indexes are still there.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top