Sign in
 
Home20122008 R2200820052000LibraryForums
SQL Server >
> 
> 
Replicated transactions are waiting for next Log backup or for mirroring partner to catch up while mirroring is never configured...

Unanswered Replicated transactions are waiting for next Log backup or for mirroring partner to catch up while mirroring is never configured...

  • Wednesday, June 20, 2012 4:25 AM
     
     
    Sign In to Vote
    0

    I have SQL Server 2008 transactional replication for 21 locations.No Mirroring is configured on this server for any database yet I am getting the error:

    Replicated transactions are waiting for next Log backup or for mirroring partner to catch up

    Due to this without taking log backup the  the log reader shows this above error and replication is not continued.

    Thanks

     

All Replies

  • Wednesday, June 20, 2012 6:47 AM
     
     
    Sign In to Vote
    0

    In log_reuse_wait and log_reuse_wait_description..from sys.databases whose tables of database is in replication I am getting..

    6, Replication in these column.

    For time being I have configured the 1 min. log backup and 1 hour deletion of this log backup from management plans.

    Please help

    Thanks

     
  • Thursday, June 21, 2012 8:54 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi Forsqlserver,

    >>Replicated transactions are waiting for next Log backup or for mirroring partner to catch up

    Regarding to the error message, do you think it would be possible to do a restart of SQL Server (So that we could apply the trace flag in the following article as a startup parameter?) What’s the edition of SQL Server you are using?

    Please apply the hotfix this may resolve your issue after you apply. This KB requires are restart of SQL Server
    For more information please refer to this KB.

    Alternatively you need to enable trace flag 1448 on the instance of the publisher database. Then, Log Reader Agent will always copy the transactions that are marked for replication from the transaction log into the distribution database.

    Note If you are running SQL Server 2008, you can also enable trace flag 1448 to resolve this issue.

    To globally enable trace flag 1448 on the instance of the publisher database, follow these steps:
    1. Start SQL Server Configuration Manager.
    2. In SQL Server Configuration Manager, click SQL Server 2005 Services.
    3. In the details pane, right-click the instance, and then click Properties.
    4. In the SQL Server (InstanceName) dialog box, click the Advanced tab, and then click Startup Parameters.
    5. At the end of the original text, type -T1448.
    6. Restart the SQL Server service.

     

    Regards, Amber zhang

     
  • Thursday, June 21, 2012 9:16 AM
     
     
    Sign In to Vote
    0

    Why this has arises while I have not mirrorirng setup.

    Is there any drawback of this trace after enabling?

    I have SQL Server 2008 STD EDTN.

    Thanks


    • Edited by Ajay.G Thursday, June 21, 2012 9:17 AM
    •  
     
  • Friday, June 22, 2012 6:55 AM
     
     
    Sign In to Vote
    0

    Hi,

    After enabling this trace the issue has not resolved.

    Any help.

    Thanks

     
  • Friday, June 22, 2012 1:42 PM
    Moderator
     
     
    Sign In to Vote
    0

    Have you backed up your tlog? It also sounds like you have configured your database for the sync with backup option.

    Can you do this:

    sp_replicationdboption 'ProblemDatabaseName','sync with backup',false

    looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

     
  • Friday, June 22, 2012 5:27 PM
     
     
    Sign In to Vote
    0

    Hi Hilary,

    Yes 'sync with backup' is true right now.

    After make it false I will tell you ...

    Will it affect the replication also?

    Thanks