Job runs for a long time and does not complete
Moderators: chulett, rschirm, roy
Job runs for a long time and does not complete
Hi all,
I imported job from windows server to linux server.After imports,i compile and run the job.
But the job is in long run state.It is not finished.There is no warnings.
I need solutions for above problem.
I imported job from windows server to linux server.After imports,i compile and run the job.
But the job is in long run state.It is not finished.There is no warnings.
I need solutions for above problem.
-
- Premium Member
- Posts: 376
- Joined: Sat Jan 07, 2012 12:25 pm
- Location: Piscataway
I'm afraid there's absolutely nothing we can do to help you unless you provide more tangible information. What does your job do? What are its sources/targets. Are you performing joins? The context of your migration activity?
Just because you 'NEED' a solution doesn't mean you'll 'GET' a solution if you don't tell us the what problem you need the solution for.
Just because you 'NEED' a solution doesn't mean you'll 'GET' a solution if you don't tell us the what problem you need the solution for.
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Sorry but all you've done is restate what was in your original post without adding any details to it. And the devil is in the details.
Please try to answer the questions Jerome posted and anything else you can think of that may prove helpful.
Please try to answer the questions Jerome posted and anything else you can think of that may prove helpful.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
In a situation like this it is often helpful to locate the "guilty" portion. Since hangs are most often in write stages, replace those in a copy of your job with simple "peek" stages and see if the job completes. If it does complete, narrow it down to the one offending stage and post details to this thread.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Premium Member
- Posts: 376
- Joined: Sat Jan 07, 2012 12:25 pm
- Location: Piscataway
I am also inclined towards a possible deadlock at the database (assuming of course that she's extracting/loading relational tables) due to open/abandoned connections. But unless she gives more data, it would be hard to put a finger on any solution.
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
What kind of stage is the target stage? What exactly is it programmed to do (for example Write Mode)?
If it's a database connector, are there any warnings generated in the database?
Do you have an after-job subroutine in your job design? If so, what does it do?
If it's a database connector, are there any warnings generated in the database?
Do you have an after-job subroutine in your job design? If so, what does it do?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: