Distribution db gone suspect!! Urgent

[nowayout]

How can i solve this error?

Please help

 

[vongrunt]

First, how it became suspect? Failed RESTORE or something?

Check sp_resetstatus in BOL... but be careful.

 

[nowayout]

in server log file it says that error while undoing logged operation in database "distribution"

then other error saying that an eeror occurred while processing the log for database"

thanks

 

[nowayout]

i don;t know but i was trying to reintialize the replication agent and in between that time it went suspect status. how can i solve this please help!!!

 

[nowayout]

the server log file also states that database 'distribution' could not recover, contact technical support!!!! please help!!!

 

[vongrunt]

To be honest, I never encountered recovery error with replication involved... what was exact error code?

 

[nowayout]

the error code is 3414.

 

[nowayout]

along witht hat is 9004 and 9001 whihc is log for db is not available.

 

[vongrunt]

I mean, prior to that... the one that refers to "error while undoing logged operation" or even earlier.

 

[nowayout]

prior to that ist says that an error occurred while processing the log for dabase "distribution"

and prior to that also it says an error occurred while procession the log for dabase "test" which was being replicated.

 

[nowayout]

will sp_resetstatus help!! what will be the implication!!or effect on rest of the database!!

Thanks

 

[vongrunt]

sp_resetstatus simply unmarks database as suspected. It doesn't solve problems by itself.

http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp

 

[nowayout]

i tried using that option but after rebooting the server it went back to suspect again!! what is the problem and what shoud i do now!!

please guide me!! totally lost now!!

 

[nowayout]

when i ran sp_resetstatus distribution i got this:

Prior to updating sysdatabases entry for database 'distribution', mode = 0 and status = 280 (status suspect_bit = 256).
For row in sysdatabases for database 'distribution', the status bit 256 was forced off and mode was forced to 0.
Warning: You must recover this database prior to access.

but i did restart the server and got the same db got suspect again.

 

[donutman]

It doesn't look like your going to get specific help, so begin thinking about your disaster recovery situation. Get your backups in order. Relax, don't panic and create a plan of action under the assumption that the database is going to become unusable. If that happens you will have improved your situation.
Once you can't do anything more in preparation, then you can begin experimentation. Can you copy the database to another server? Can you copy the entire server (eg. at night) to another server? Does that fix the database? Etc.
-Karl

[red] Cursors, triggers, user-defined functions and dynamic SQL are an axis of evil![/red]
[green]Life's uncertain...eat dessert first...www.deerfieldbakery.com[/green]

 

[nowayout]

i don;t have back up of this database so can i recover this db from different db server distribution database?

i am trying to clam but you know the situation now!! cuz there is no backup of this database from starting with!!

what is your suggestion now!!

 

[nowayout]

i ran the reset status again but did not restarted the server but if i try to open the table then it tells me that can't open database in suspect.

what is there that i can do!!