Damaged Sysindexes - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

Data Corruption Issues

Damaged Sysindexes

Author

Topic

tkaub
Starting Member

3 Posts

Posted - 2005-10-17 : 09:17:22

Hi,
Please note that I'm having the below problem:

1- when i run "DBcc CheckDB ('DBName') with all_errormsgs"
I Get:
Could not read and latch page (1:173) with latch type SH. sysindexes failed.

2- then :
select * from sysindexes

Gave me:
I/O error (torn page) detected during read at offset 0x0000000015a000 in file 'C:\Data\Databases\Old_Data.MDF'.

Connection Broken

3- dbcc checktable ('sysindexes')
Could not read and latch page (1:173) with latch type SH. sysindexes failed.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 2, index ID 0, page (1:173). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.CHECKTABLE found 0 allocation errors and 1 consistency errors in table 'sysindexes' (object ID 2).

Forth of all, I can't use a backup because it is old.
Can i copy system tables from old database to the current one that we are using...

I tried to export and import data from this corrupted database but it would give me errors...

Is there anyway that i can adjust this database.
Please Help Urgently....

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2005-10-17 : 12:01:02

I'm afraid you have no choice but to use a backup.

This error cannot be removed by any means - it's a torn page (hardware only wrote out part of a page) in one of the critical system tables. There's also no way to work around this error as the data on the page in question has been destroyed. My guess is that you took a power outage?

So, no matter how old your backup is, you must use it. Learn from this lesson and formulate a workable backup strategy.

Thanks

Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2005-10-17 : 12:05:41

Actually, you could try the method outlined in the original thread you posted to - you may be able to salvage data from tables who's metadata is not rooted on the corrupt page - but if that works you're still going to lose a whole bunch of tables from your database.

Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2005-10-17 : 13:18:31

you say you can't export data from this db in any way??
if you can query your tables in QA you can simply select all data and copy paste it to a text file...
at least it beats losing the data....

Go with the flow & have fun! Else fight the flow

tkaub
Starting Member

3 Posts

Posted - 2005-10-17 : 14:00:34

Dear Mr. Paul,
Thanks for your advise
but please note that this was the only data that was recovered from a damaged Hard Disk.
anyway, and Backups are kind off old.
so i'm in a really big mess...

Regards and
Thanks in advance.
T.K.

quote:
Originally posted by paulrandal

I'm afraid you have no choice but to use a backup.

This error cannot be removed by any means - it's a torn page (hardware only wrote out part of a page) in one of the critical system tables. There's also no way to work around this error as the data on the page in question has been destroyed. My guess is that you took a power outage?

So, no matter how old your backup is, you must use it. Learn from this lesson and formulate a workable backup strategy.

Thanks

Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2005-10-18 : 12:36:41

You have no choice:

1) try to extract as much as you can manually
or
2) restore from your backup

There's nothing else you can do.

Whatever you do, I suspect you'll be also working on a useful backup strategy too.

Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)

babayaga
Starting Member

1 Post

Posted - 2009-03-19 : 15:34:54

quote:
Originally posted by paulrandal

I'm afraid you have no choice but to use a backup.

This error cannot be removed by any means - it's a torn page (hardware only wrote out part of a page) in one of the critical system tables. There's also no way to work around this error as the data on the page in question has been destroyed. My guess is that you took a power outage?

I just saw your poste about the power issue. I have the same error message (faluty sysindex). But all I did was going command line
and write
copy tplsql.mdf and the log file to another directory,
files i collected seems to be corrupt, but this could be the copy it selfe, or error on disk? I just can't believe I managed to destroy a DB by useing "copy *.* C:\tempsql"

Or atleast NOT the source file i copied off.?

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2009-03-19 : 15:46:25

Yes, if the section of disk you copied the files to had issues and corrupted the files.

Paul S. Randal, Managing Director, SQLskills.com (www.SQLskills.com/blogs/paul)
SQL Server MVP, Contributing Editor of TechNet Magazine
Author of SQL 2005 DBCC CHECKDB/repair code
Author & Instructor of Microsoft Certified Master - Database course

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources