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

How can i resolve undistributed commands in Transaction replication Expand / Collapse
Author
Message
Posted Wednesday, January 2, 2013 5:37 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 6:45 AM
Points: 94, Visits: 319

Hi,

We are reconfigured publication and subscription but undistributed commands to subscriber is showing very huge

No command to be distributed :7777


Please find the attachment....Help me how can i resolve this


  Post Attachments 
image001.png (21 views, 4.50 KB)
Post #1401795
Posted Wednesday, January 2, 2013 5:54 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, March 19, 2014 5:28 AM
Points: 102, Visits: 1,050
Hi Friend,

If the number of undistributed commands was very high and increasing. Go and restart the sql server agent at the distributor, and like magic the undistributed commands was back down to 0 again.



Regards,
Kumar
Post #1401800
Posted Wednesday, January 2, 2013 6:42 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 6:45 AM
Points: 94, Visits: 319
These commands need to be apply at subscriber right then how can i restart SQL Server Agent.....Is this resolve this kind off issues.

What it mean by undistributed commands. If i restart agent, How to these can be applied to subscribers.

In Replication monitor, Status of Subscriptions are showing as Uninitialized subscribers.

Post #1401814
Posted Wednesday, January 2, 2013 7:20 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, March 19, 2014 5:28 AM
Points: 102, Visits: 1,050
From the replication monitor as you can see the value for Performance critical, Expiring soon/Expired, and Uninitialized subscription are warnings. When a warning is displayed, the Status column also displays if an agent is running. For example, the status could be Running, Performance critical. So confirm whether you see any value in Status column.

I believe the below steps wil answer for your queries..
1.I stopped SQL Server Agent on my Distribution server in order to effectively stop all replication jobs (although I probably could have manually stopped each of the individual replication jobs instead).
2.I re-ran EXEC dbo.sp_MSdistribution_cleanup @min_distretention = 0, @max_distretention = 1 in order to clean-up the distribution history older than 1 hour. This outputted that no transactions were removed.
3.I re-ran sp_browsereplcmds and saw that I still had a number of transactions in MSrepl_commands.
4.I restarted SQL Server Agent which restarted all the replication jobs.
5.Magically, the undistributed commands went to zero!
6.A quick re-run of sp_browsereplcmds showed that I still had the same number of transactions in MSrepl_commands. I


Regards,
Kumar
Post #1401828
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse