Psst! Did you know DevelopmentNow is a mobile web site design agency?

Contact us for help mobilizing your site, or to sign up for our beta Mobile Web SDK!
all groups > sql server replication > december 2003 >

sql server replication : Agent is suspect



kimld1314
12/14/2003 11:33:49 AM

We have transactional replication running from SQL Server 2000 to Oracl
8.1.7.3. The log reader and distribution jobs are setup to run every
minutes. The following error is being encountered intermittently:

The agent is suspect. No response within last 30 minutes.

Our profile is as follows:

BcpBatchSize 200,000
CommitBatchSize 50,000
CommitBatchThreshold 50,000
HistoryVerboselevel 1
KeepAliveMessageInterval 30
LoginTimeOut 15
MaxBcpThreads 1
MaxDeliveredTransactions 0
PollingInterval 10
QueryTimeOut 900
SkipErrors
TransactionsPerHistory 100

When the agent goes suspect it hangs the distribution job until w
cancel/stop the job. I have changed the Inactivity Threshold from 1
to 30 minutes but still get the error above. I also checked the lo
reader agent for the same time period of that the agent went suspec
but there were no transactions identified. I also have th
distribution jobs setup to notify us when they fail but the job is no
failing but continuously running.

Is there something I am missing

kimld131
-----------------------------------------------------------------------
Posted via http://www.mcse.m
-----------------------------------------------------------------------
View this thread: http://www.mcse.ms/message180405.htm
chris
12/15/2003 8:49:27 AM
Can you double click the agent in the right pane of EM and
see any error messages that led up the non-response?


[quoted text, click to view]
Hilary Cotter
12/15/2003 3:29:23 PM
what this means is that the process which is running on the subscriber is
taking longer than the 10 minutes Microsoft allotted for it. Sort of similar
to the feeling you get when you don't hear from you girlfriend/boyfriend for
a long time, you start to wonder.

bump up your querytimeout value to something high and restart your process.
This could be a normal occurence or possibly symptomatic of something large.

[quoted text, click to view]

Sri
12/17/2003 4:14:53 PM
Open the "refresh rate and settings" by rightclicking on replication
monitor. Increase the inactivity thresold.

Sri

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.
Don't see what you're looking for? Try a search.
View other messages about sql server replication
AddThis Social Bookmark Button
View Other Months
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
October 2008