January 19, 2010 at 6:38 pm
Hello
I am doing the replication and the subscription synchronization status
shows "Time out Expired". When the job is running i check dbcc opentran,
MSdistribution_history , MSlogreader_history and the output shows
successful replication. I am committing every 20,000 rows and the
pull subscription runs continuously. I am loading 10+GB/day and
occasionally it hangs at the publisher and the subscriber agent
shows "Timeout Expired". Publisher shows The process is running and is
waiting for a response from one of the backend process. When i restart
the Synchronization job it continues successfully and completes.
How do i find what is causing it. I monitored the CPU / Memory usage
and it does not go above 20% ever. 99% of the time the CPU is used
only 2-3%. There is approximately 40% memory free at any given time.
TIA
January 20, 2010 at 6:25 pm
The retry option at the Pull Subscription agent seems to take care of this. The following articles might be of help.
PRB: Log Reader Agent Does Not Function and You Receive an Error Message During Transaction Replication
http://support.microsoft.com/kb/811030
FIX: Logreader Fails with "...Could Not Execute Sp_replcmds.." Error Message
January 25, 2010 at 6:35 pm
Fine, i am back to square one. The problem re-surfaced again. Have anyone tried pssdiag in SQL Server 2008? I am not seeing one available on line. Only for SS2005 it seems to be available. This involves about 15GB of data replication. Does anyone know how much volume of log the PSSDIAG generates?
TIA
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply