March 31, 2014 at 10:23 am
Hi,
This weekend one of our publications expired and needed to be reinitialized. We found this out when it started causing a production issue even though we have the "Warn if a subscription will expire within the threshold" and "Warn if latency exceeds the threshold. These alerts are triggered if error 14160 and 14161. After looking through logs and some replication tables I only found records of error 14151 and 14152 which are tied to the Replication: Agent jobs. Error 14151 reports that a subscription has been marked inactive and I see a lot of these going many months back, but most of them over this weekend a day or two before the issue.
Since I can't find an error 14160 my guess is it was never created and therefore no alert was triggered. Has anyone seen this, in what table should I look for these errors? We are worried this will happen again. The publication is set to not expire until 336 hours of inactivity but the timeout errors are not contiguous for 2 prior weeks and I think we would have noticed sooner if it had already been expired two weeks. I can give you more information if you need it. Thanks!
One more thing, what does it mean the subscription will expire within a threshold, when the threshold is set to a percent? For example, 80% of what?
April 1, 2014 at 7:58 am
For what its worth I've always encountered similar issues with replication alerts not firing, unless I manually scripted it out in TSQL, setting the "@shouldalert = 1"
When done via the GUI - I've never had it work properly.
For example:exec [distribution]. sys.sp_replmonitorchangepublicationthreshold
@publisher = N'SERVER',
@publisher_db = N'DATABASE',
@publication = N'PUBLICATION',
@metric_id = 2 , --metric_id 1=latency, 2=subscription expire
@value = 3600 , --Enter Threshold here
@shouldalert = 1 ,
@mode = 1
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
April 1, 2014 at 9:23 am
Thanks,
I have already found this stored procedure and set the shouldalert to 1. I have deleted a table in the subscription so that they would become out of sync and waited a while, but the only error message I saw was related to the agent failing. I still never received an alert about a threshold close to expiring. I set it to expire in 1 hour and the threshold to 5% which is about 3 minutes. Think it just doesn't work..... seems everywhere I look people have the same problem.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply