June 10, 2009 at 11:23 am
we have a job on a server that runs every minute between 3am and 11:59pm. it's a simple copy of data from a sybase server.
today we see that it hadn't run since last night and one of the job history entries had a duration of -3976.20:00:52. looks like two instances of the same job started at 11:50pm, one finished and the other had a step start at 11:40pm. this second one says it finished successfuly as well, but it didn't run when scheduled today. no errors anywhere.
June 10, 2009 at 11:27 am
I've never seen two instances of a job running overlapped, but this doesn't mean it's impossibile.
What does msdb.dbo.sp_help_jobhistory return? Same results as SSMS?
-- Gianluca Sartori
June 10, 2009 at 12:23 pm
checked it and there are a few instances where the run_duration is -954439548
it will start two instances at the same time. one will finish OK and the other one will show steps 2-5 starting before step 1
June 11, 2009 at 6:21 am
Looks very strange...
Can you post a sample of the overlapped job history records?
-- Gianluca Sartori
October 26, 2009 at 4:10 am
Hello !
I Had the Same Problem, The same Day.
I Think it's because of the summer Time change (I'm In France), so that the Job EndTime is before StartTime, and MSSQL Don't know how to manage it.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply