SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Negative Run Duration


Negative Run Duration

Author
Message
Brian Munier
Brian Munier
Right there with Babe
Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)

Group: General Forum Members
Points: 761 Visits: 80
I am using SQL Server 2000 Enterprise Edition, Sp4 + Hotfix on a properly configured Windows 2003 Server R2 with 10 GB Ram on a two-node active-active cluster.

I have had my Job history report durations of:
-95443:-92:-42

Any thoughts?
Steve Jones
Steve Jones
SSC Guru
SSC Guru (146K reputation)SSC Guru (146K reputation)SSC Guru (146K reputation)SSC Guru (146K reputation)SSC Guru (146K reputation)SSC Guru (146K reputation)SSC Guru (146K reputation)SSC Guru (146K reputation)

Group: Administrators
Points: 146442 Visits: 19430
Sounds like a bug.

Is this the first time the job was run? Have you checked the raw data in the msdb tables?

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
george sibbald
george sibbald
SSC-Insane
SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)

Group: General Forum Members
Points: 24614 Visits: 13698
I got exactly this run timing on a job that kicked off at exactly the time the clocks went back. Any differences in system time between the nodes. sounds like SQLAgent thinjs the job finished before it started, if you see what I mean.

---------------------------------------------------------------------
Brian Munier
Brian Munier
Right there with Babe
Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)

Group: General Forum Members
Points: 761 Visits: 80
Thank you both.
First the job has been running for years. Second I thought we dealt with the DST back in the spring on this server.

It is still occuring, any thoughts on how to stop it? Re-do the job or maintenance plan?

Thanks in advance, I am glad to know I am not crazy.

Brian
george sibbald
george sibbald
SSC-Insane
SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)

Group: General Forum Members
Points: 24614 Visits: 13698
what does the job do? is it long running or a quick job, how is it kicked off?

---------------------------------------------------------------------
Steve Jones
Steve Jones
SSC Guru
SSC Guru (146K reputation)SSC Guru (146K reputation)SSC Guru (146K reputation)SSC Guru (146K reputation)SSC Guru (146K reputation)SSC Guru (146K reputation)SSC Guru (146K reputation)SSC Guru (146K reputation)

Group: Administrators
Points: 146442 Visits: 19430
Can you query the raw data in msdb and see what's listed? sysjobhistory?

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Brian Munier
Brian Munier
Right there with Babe
Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)

Group: General Forum Members
Points: 761 Visits: 80
Ok, let's see the job is a transaction log backup part of a maintenance plan.

The maintenance plan is actually created by LiteSpeed enterprise edition version 4.5.204.

I am running this setup on several different server (16) in several different clusters. I haven't noticed the problem on other servers, but I will double check.
Brian Munier
Brian Munier
Right there with Babe
Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)

Group: General Forum Members
Points: 761 Visits: 80
And to answer the other question, yes the raw data is in the msdb sysjobhistory table where the run duration is negative.
Steve Jones
Steve Jones
SSC Guru
SSC Guru (146K reputation)SSC Guru (146K reputation)SSC Guru (146K reputation)SSC Guru (146K reputation)SSC Guru (146K reputation)SSC Guru (146K reputation)SSC Guru (146K reputation)SSC Guru (146K reputation)

Group: Administrators
Points: 146442 Visits: 19430
Very strange. Is it only the Litespeed jobs?

I wouldn't think that Litespeed has anything to do with it. The only thing that would make sense would be a time adjustment during the job, something like the DST change. How long does it take for the job to run?

Is this still continuing? What if you manually run the job now?

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Brian Munier
Brian Munier
Right there with Babe
Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)Right there with Babe (761 reputation)

Group: General Forum Members
Points: 761 Visits: 80
It is primarily the LiteSpeed transaction backup job, which runs every 15 minutes, but I just found one instance in a job that was manually created to purge the old backup history. So I would agree it is not LiteSpeed.

I will have to double check time sources as we do try to keep them synched. maybe one of them is off.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search