Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Standby Database Reverting to Suspect Expand / Collapse
Author
Message
Posted Friday, May 28, 2010 5:38 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Thursday, September 19, 2013 4:24 AM
Points: 78, Visits: 144
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
Post #929593
Posted Friday, May 28, 2010 9:54 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 2:24 PM
Points: 40,667, Visits: 37,129
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 2008, MVP
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

Post #929806
Posted Wednesday, June 2, 2010 8:01 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Thursday, September 19, 2013 4:24 AM
Points: 78, Visits: 144
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.
Post #931366
Posted Wednesday, June 2, 2010 11:49 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 2:24 PM
Points: 40,667, Visits: 37,129
Also check for any errors reported from the IO subsystem.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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

Post #931557
Posted Thursday, September 19, 2013 1:49 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 12:59 AM
Points: 2, Visits: 64
Hi !
I think your database is corrupted,so please take fresh full backup and restore it .it will work for your case
Post #1496247
Posted Thursday, September 19, 2013 4:23 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 2:24 PM
Points: 40,667, Visits: 37,129
Please note: 3 year old thread.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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

Post #1496294
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse