Sequence gone haywire
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 1044
- Joined: Wed Sep 29, 2004 3:30 am
- Location: Nottingham, UK
- Contact:
Sequence gone haywire
I have a Sequence that just runs a load of jobs one after another unconditionally. Last night it went wrong and tried to launch one of the jobs twice, and errrored because "Job is not in the right state (compiled and not running)". Anyone seen this happen before? One of my colleagues added a job to the sequence yesterday, but that's further down the chain, it didn't get that far.
Is it possible that running a job of the same name in another project might confuse the Job Schedule?
I had a similar problem a couple of years ago, it did something like this:
1. Tell the server to start running the job
2. Check that the job is running - no it isn't, ERROR!
3. Job starts running
Just a timing issue I think, but annoying.
Is it possible that running a job of the same name in another project might confuse the Job Schedule?
I had a similar problem a couple of years ago, it did something like this:
1. Tell the server to start running the job
2. Check that the job is running - no it isn't, ERROR!
3. Job starts running
Just a timing issue I think, but annoying.
Phil Hibbs | Capgemini
Technical Consultant
Technical Consultant
Re: Sequence gone haywire
Nope. Are you certain the Sequence itself tried to start the job twice? Any chance someone/thing else started it before your Sequence did?PhilHibbs wrote:Is it possible that running a job of the same name in another project might confuse the Job Schedule?
ps. Don't recall ever seeing anything like this.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Premium Member
- Posts: 1044
- Joined: Wed Sep 29, 2004 3:30 am
- Location: Nottingham, UK
- Contact:
Screenshots of it working ok on Tuesday but going wrong last night:
http://www.hibbs.me.uk/images/sequence_ok.png
http://www.hibbs.me.uk/images/sequence_haywire.png
http://www.hibbs.me.uk/images/sequence_ok.png
http://www.hibbs.me.uk/images/sequence_haywire.png
Phil Hibbs | Capgemini
Technical Consultant
Technical Consultant
-
- Premium Member
- Posts: 1044
- Joined: Wed Sep 29, 2004 3:30 am
- Location: Nottingham, UK
- Contact:
I'll let you know - we can only run this job after 6pm as it accesses a mainframe system with expensive daytime mips.chulett wrote:Is this a repeatable behaviour with the modified version of the Sequence or was it a one time thing? I'll guess we may have to wait and see.
Phil Hibbs | Capgemini
Technical Consultant
Technical Consultant
Did you check to see if that particular job ran or any log for that particular day? It seems like the job just refused to obey its master.
Wait and see if the error is repeatable. Then maybe some
will pop up to debug it.
Also, make sure your keeping the &PH& folder in check so that we can rule out the chance of any sort of timeouts.
Wait and see if the error is repeatable. Then maybe some
![Idea :idea:](./images/smilies/icon_idea.gif)
Also, make sure your keeping the &PH& folder in check so that we can rule out the chance of any sort of timeouts.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
What was the change exactly?
Was a Job added in that Sequence at the tail, Recompiled the secquence as well as Job and imported into new project?
Or only the Executable got imported?
Wasn't there any change in the Job which the Sequence is complaining?
Was a Job added in that Sequence at the tail, Recompiled the secquence as well as Job and imported into new project?
Or only the Executable got imported?
Wasn't there any change in the Job which the Sequence is complaining?
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Yes. Delete old files. There is no debugging info in those files. They are just phantom files. Most folks have a script that runs daily and deletes all files 7 days and older. If the &PH& file is left unchecked ('without deleting old files'), this effects the startup times of jobs.
Warning: Make sure you delete only old files, please dont accidentally, delete any files for jobs currently running.
Warning: Make sure you delete only old files, please dont accidentally, delete any files for jobs currently running.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
-
- Premium Member
- Posts: 1044
- Joined: Wed Sep 29, 2004 3:30 am
- Location: Nottingham, UK
- Contact:
The change was that another job was included in the sequence, about three or four steps further on in the line than the position that it all went wrong. I don't think there was any change to the job that the Job Sequence trued to run twice. Even if there was, changing a job shouldn't cause the Sequence to run it twice simultaneously when it's only in the sequence once.kumar_s wrote:What was the change exactly?
Was a Job added in that Sequence at the tail, Recompiled the secquence as well as Job and imported into new project?
Or only the Executable got imported?
Wasn't there any change in the Job which the Sequence is complaining?
Phil Hibbs | Capgemini
Technical Consultant
Technical Consultant
-
- Participant
- Posts: 82
- Joined: Tue Jan 22, 2008 10:37 am
- Location: UK
I don't think this ran 1 job twice, it ran 2 jobs at the same time:
MM_COLORS_LFA1_Tbl_EXT &
MM_COLORS_LXX_Extract
Does the 2nd job depend on data being landed by the first job ? - take a look at the specific log for this job, you might get more of a clue.
And see if the sequence has been changed to not wait for the first job before starting the 2nd one.
MM_COLORS_LFA1_Tbl_EXT &
MM_COLORS_LXX_Extract
Does the 2nd job depend on data being landed by the first job ? - take a look at the specific log for this job, you might get more of a clue.
And see if the sequence has been changed to not wait for the first job before starting the 2nd one.
-
- Premium Member
- Posts: 1044
- Joined: Wed Sep 29, 2004 3:30 am
- Location: Nottingham, UK
- Contact:
At 18:10:45 you can see "Waiting for job MM_COLORS_LXX_Extract to start", and then at 18:11:09 it tries to call DSRunJob(MM_COLORS_LXX_Extract ) and fails because it's already running.deanwalker wrote:I don't think this ran 1 job twice, it ran 2 jobs at the same time
None of the jobs depend on each other, they are all source system extracts into flat files. The only reason I sequence them is so that they don't all run at the same time and overload the source system.
Phil Hibbs | Capgemini
Technical Consultant
Technical Consultant
-
- Participant
- Posts: 82
- Joined: Tue Jan 22, 2008 10:37 am
- Location: UK