Standby Database Reverting to Suspect

Question

Standby Database Reverting to Suspect

Martin Hawley

SSChasing Mays

Points: 650
More actions
May 28, 2010 at 5:38 am

#235713

I have a server containing 25 databases with log shipping set up to a secondary site and scheduled to run every 15 minutes. It is regularly returning error messages which result in the standby databases reverting to a status of suspect. The error messages are along the lines of :- "The log scan number (xxx:xx:x) passed to log scan in database 'XXXXXXX' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from the backup if the problem results in a failure during startup."
Does anyone know of any reason for this happening and how I can prevent it?
TIA
Martin

Viewing 6 posts - 1 through 5 (of 5 total)

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

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

From the sound of the error, there's corruption in the transaction log. Drop the affected databases and reconfigure log shipping for those DBs from scratch.

Also, do some checks of the IO subsystem on that server, look for any errors, misconfigurations, warnings or alerts. Corruption is typically an IO subsystem problem.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Martin Hawley SSChasing Mays Points: 650 More actions · Answer 2

Thanks, we were rebuilding the DBs from scratch, but the errors keep reoccurring.

After a bit more research I turned up this article: http://support.microsoft.com/kb/940126. As we are on SP2, looks like applying Service Pack 3 should resolve the problem.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 3

Also check for any errors reported from the IO subsystem.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

shyamalarakesh Newbie Points: 8 More actions · Answer 4

Hi !

I think your database is corrupted,so please take fresh full backup and restore it .it will work for your case

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 5

Please note: 3 year old thread.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass