Corrupted Database Error 3456

Question

After a simple reboot of the file server one of the data bases in the Sql Server 2k of the SBS 2000 appears in enterprise manager as supect. I decided to detach and again to attach the db. I have never been abble to attach the db, and I received teh following error:

Error 3456: could not redo log record(8433:539:79), for transaction ID:(0:0), on page(1:32352), database 'PRICAI2005' (9). Page: LSN=(8432:16085:7), type=11.log: UpCode=5, context 11, PrevPageLsN:(8433:378:3).

I think I have read all kind of information about this error, I tried all th sugestions in the multiples articles I saw, but untill now, the problem  remains the same. And no, I haven't any backup of this DB. Is there anyone who knows a solution for my problem. I will be deeply gratefull.

 

Thanks,

José Dinis 

[e-mail]

Answer 1

Hi Jose,

i would suggest you to refer the best article i have found for restoring status of suspect database , it was by Svetlana Kuvshinkova
http://www.myitforum.com/articles/18/view.asp?id=7381

and also refer below threads

http://sqljunkies.com/Forums/ShowPost.aspx?PostID=11566

and http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=11689&#55322

 

HTH

Hemantgiri S. Goswami

Answer 2

Do you have a backup for this database?

KBA http://support.microsoft.com/kb/831950 & http://support.microsoft.com/kb/826433 fyi.

Answer 3

i am facing the same problem on log shipped database. please guide me

---

Manish

Answer 4

here i don't have clean backups 

---

Manish

Answer 5

If this secondary server database or primary database?  Since log shipping is configured, you would have backups and you can restore them.

What's the version of SQL Server?

---

Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
--------------------------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------------------------------------------------------------------
My Blog | Team Blog | @Twitter