Transaction Log Sequence Broken....

  • Hi All,

    T.log can not be restored on the secondary Database which is due to that transaction log sequence is broken.in that time what we will check & do .

    Please give me some suggestions.

    Regards

    Jagadeesh...

    Regards
    Chowdary...

  • Reinitialise the log shipping. Investigate why the log chain was broken

    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
  • You have to restart. There's no way to recover in place once the chain is broken.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • Chowdary's (7/11/2014)


    Hi All,

    T.log can not be restored on the secondary Database which is due to that transaction log sequence is broken.in that time what we will check & do .

    Please give me some suggestions.

    Regards

    Jagadeesh...

    Have you taken a full backup at the source since the LS broke, if not then a differential backup and restore to the LS secondary will kick the LS plan back into sync

    Check the differential base LSN on primary and secondary using

    select DB_NAME(database_id), differential_base_lsn

    from sys.master_files

    where database_id = DB_ID('your primary\secondary LS db')

    and type_desc = 'rows'

    group by database_id, differential_base_lsn

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

Viewing 4 posts - 1 through 3 (of 3 total)

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