DB Attach-Detach problem

Question

Post reply

DB Attach-Detach problem

Harcharan Jassal

SSC Veteran

Points: 296
More actions
April 20, 2005 at 7:35 am

#165277

Hi Experts!!!
After some patches were applied by Network Adminstrator, one of my database got into suspect mode. I tried to detach and re-attach the database, but I get the following error:
" I/O error (bad page ID) detected during read at offset 0x00000000030000 in file 'E:\NLGDATA\XYZ_Data.MDF'.
Connection Broken "
Is there a way to get this Database up again? Unfortunately I donot have a backup as this DB was used for some test purpose and I never realised it contains few tables which are used used as a connection string for a OLAP Database in analysis server.
Please mail me any answers at hjjassal@yahoo.com
Regards,
Harry

Viewing 4 posts - 1 through 3 (of 3 total)

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

Clark Cruz-131251 SSC Journeyman Points: 82 More actions · Answer 1

I have also experienced this error. Unfortunately, I did not find a work around for the problem.

Jim P. SSCrazy Eights Points: 8725 More actions · Answer 2

MS KB articles:

PRB: Error message 823 may indicate hardware problems or system problems

and

PRB: Additional SQL Server Diagnostics Added to Detect Unreported I/O Problems

They both suggest hardware problems are the cause.

The one link suggests trying a "DBCC CHECKDB" might work. If it doesn't I think you pretty much have lost the db.

You can always try dumping the $245 with MS but I don't think it will really help much. I think this is pretty much in the class of Torn Pages - - take the loss and learn from it - always backup!

Sorry for the bad news.

----------------
Jim P.

A little bit of this and a little byte of that can cause bloatware.

peterhe SSChampion Points: 11469 More actions · Answer 3

I encountered several times of suspect db. What I did were:

1) Made it online first of all.

A database can become suspect for several reasons.

Try

EXEC sp_resetstatus 'DB_Name'

first to reset its status and restart SQL server.

If it does not work, try to rebuild the log file:

Sp_configure allow, 1

Go

Reconfigure with override

Go

Update sysdatabases set status = 32768 where name = 'DB_name'

-- SQL 6.5, -32768; SQL 7.0 or 2000, 32768

go

--dbcc rebuild_log(Db_Name, new_log_file)

dbcc rebuild_log('db_name','new_log_file_name')

GO

Sp_configure allow, 0

Go

Reconfigure with override

Go

2) If the first step succeeded, run dbcc checkdb. If there are errors reported, change the db to single user mode and run dbcc checkdb with repare options. You may need to repare several times.

3) Backup database. Run disk utility to check disk damage if necessary

Good luck.