February 19, 2009 at 12:04 pm
Hi ,
I am getting this alert from my server which is principal server.
DATE/TIME: 2/19/2009 1:37:00 PM
DESCRIPTION: The alert for 'time behind' has been raised. The current value of '96' surpasses the threshold '5'.
COMMENT: Concur Apps: The age of unsent transaction log in one of Concur App databases has reached threshold of 5 min.
JOB RUN: (None)
Any suggestions how to solve above alert ?
Thanks
Ichbinraj
February 19, 2009 at 12:17 pm
If you put the alert message into Google/Live/whatever, it comes up with a couple of articles on MSDN on what that means and what to do about it.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
February 19, 2009 at 12:36 pm
Hi ..
I am not sure why this alert is coming ...
I have servers A and server B involved in mirroring ..
suddenly Server A sending alerts to my emil id .. I tried in google and not able to find relevant information .. that's why I am putting in forums.. in event viewer i found
Event Viewer /Application Log message :The Alert for 'time behind' has been raised'. The Current Value of '135' surpasses the threshold '5'
information realted this problem : http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=SQL%20Server&ProdVer=9.0&EvtID=32040&EvtSrc=MSSQLServer&LCID=1033
Searching for how to stop this alerts. appreciate your suggestions.
Thanks
Ichbinraj
February 19, 2009 at 12:48 pm
I searched for "The alert for 'time behind' has been raised" in Live Search.
The second result was http://msdn.microsoft.com/en-us/library/aa337363(SQL.90).aspx.
That page has this to say about it:
Explanation
This database mirroring event is issued on the principal server instance to indicate that the age of the oldest unsent transaction has reached a user-specified threshold value. Typically, this event occurs because the performance of the system has changed. Either the bandwidth between the two systems has decreased, or the load has increased.
The age of the oldest unsent transaction is a performance metric that can help you evaluate the potential for data loss as measured by the number of minutes of unsent transactions. This metric is especially relevant for high-performance mode sessions. However, this metric is also relevant for high-safety mode session when mirroring is paused or suspended because the partners become disconnected.
User Action
Check the loads on the principal and mirror server instances and their network connection for the cause.
See Also
Other Resources
Database Mirroring Sessions
Using Warning Thresholds and Alerts on Mirroring Performance Metrics
So, it seems to me that what you need to do is check the load on the two servers and on their network connection and see if it's too much.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
April 7, 2009 at 7:38 am
I'm having a similar problem, here's my situation:
Oldest unsent transaction is 3:50:00 and climbing but unsent log is 0KB. I find this odd, if the there is a transaction sitting there, shouldn't the unset log have some size to it?
All the other values (ie current send rate, unrestored log, current restore rate, etc) are zero. So it's doing no transfer whatsoever. The current state of this database says synchronized though.
The servers are barely taxed at all, CPU is averaging 10%. There is enough space on each server. The bandwidth between the two should be more than sufficient, right now only 1 database is transferring, the other 6 are not.
I'm wondering if there is something to be concerned about if the unsent log = 0KB, but then again why is the oldest unsent transaction almost 4 hrs old?
I tried Pausing the mirror and resuming, it transferred for a second, but went back to 0 and the values didn't change (unsent log, oldest unsent trans, etc). The current state says synchronizing, but again nothing is being sent.
Can someone help shed some light? Your help is much appreciated!!!
July 20, 2010 at 7:49 am
Did you ever find out the issue? I'm experiencing the exact same thing.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply