Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 123»»»

Negative Run Duration Expand / Collapse
Author
Message
Posted Thursday, November 29, 2007 1:26 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, October 04, 2012 11:13 AM
Points: 257, 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?
Post #427754
Posted Sunday, December 02, 2007 1:30 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 6:29 PM
Points: 32,834, Visits: 14,975
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
Post #428533
Posted Monday, December 03, 2007 5:38 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 2:26 PM
Points: 5,850, Visits: 12,599
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.

---------------------------------------------------------------------

Post #428674
Posted Monday, December 03, 2007 5:42 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, October 04, 2012 11:13 AM
Points: 257, 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
Post #428676
Posted Monday, December 03, 2007 5:46 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 2:26 PM
Points: 5,850, Visits: 12,599
what does the job do? is it long running or a quick job, how is it kicked off?

---------------------------------------------------------------------

Post #428680
Posted Monday, December 03, 2007 7:57 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 6:29 PM
Points: 32,834, Visits: 14,975
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
Post #428749
Posted Tuesday, December 04, 2007 7:12 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, October 04, 2012 11:13 AM
Points: 257, 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.
Post #429269
Posted Tuesday, December 04, 2007 7:14 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, October 04, 2012 11:13 AM
Points: 257, Visits: 80
And to answer the other question, yes the raw data is in the msdb sysjobhistory table where the run duration is negative.
Post #429270
Posted Tuesday, December 04, 2007 7:33 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 6:29 PM
Points: 32,834, Visits: 14,975
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
Post #429288
Posted Tuesday, December 04, 2007 7:40 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, October 04, 2012 11:13 AM
Points: 257, 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.
Post #429298
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse