Corrupted transaction log | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Corrupted transaction log

I have a log shipping configuration that has been running fine until a reindex task was ran on the database while one of the transaction log backups was being created. Now this transaction log file won’t restore to the secondary server, and the subsequent transaction log backups are stacking up. How can I get around this without having to restore a complete database backup and starting log shipping all over again? Is there such a way? Thanks,
Ken
If the sequence of Transaction log is broken due to a corrupted log file, then in order to get the sequence back you must restore the complete database backup from primary server to the secondary server. What was the error while restoring try to take anothe Transaction log backup and apply on secondary server. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
I was afraid that was going to be my only solution. At least it wasn’t in production yet! <br /><br />The error message when it attempted to load this particular log file was:<br />Could not redo log record (xxxxx<img src=’/community/emoticons/emotion-12.gif’ alt=’:x’ />xxxx<img src=’/community/emoticons/emotion-12.gif’ alt=’:x’ />), for transaction ID (x<img src=’/community/emoticons/emotion-12.gif’ alt=’:x’ />xxxxxxxx), on page (x<img src=’/community/emoticons/emotion-12.gif’ alt=’:x’ />xxxxxx), database ‘dbname’ (7). Page: LSN = (xxxxxx<img src=’/community/emoticons/emotion-12.gif’ alt=’:x’ />xxxx<img src=’/community/emoticons/emotion-12.gif’ alt=’:x’ />), type = 1. Log: OpCode = 4, context 2, PrevPageLSN: (xxxxxx<img src=’/community/emoticons/emotion-12.gif’ alt=’:x’ />xxx<img src=’/community/emoticons/emotion-12.gif’ alt=’:x’ />)..<br /><br />Followed by<br />Error: 3456, Severity: 21, State: 1<br /><br />Thanks for the input!<br />Ken
If the corruption due to the hardware and other I/O issues, then refer to this KBAhttp://support.microsoft.com/default.aspx?kbid=826433 to add more diagnostic tools. Error 3456 is the generic for the log shipping due to breakup of log restor sequence.
HTH Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>