Jobs keeps running even though the Mload has failed
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 36
- Joined: Wed Aug 09, 2006 12:18 am
- Location: Chennai
Jobs keeps running even though the Mload has failed
Hi All,
Issue : The Jobs keeps running even though the Mload has failed.
1.I am loading a table through a Mulitload stage in datastage
2.Due to some reasons if the Multiload fails and the Mulitload log shows an error code, the job doesnt abort it keeps on running.
3.After seeing the Mload log i have to abort the job manually.
4.The data volume does not matter.
Any Workarounds?
Regards,
Issue : The Jobs keeps running even though the Mload has failed.
1.I am loading a table through a Mulitload stage in datastage
2.Due to some reasons if the Multiload fails and the Mulitload log shows an error code, the job doesnt abort it keeps on running.
3.After seeing the Mload log i have to abort the job manually.
4.The data volume does not matter.
Any Workarounds?
Regards,
Sakthi
One work around would be, call the job, through a JobSequence. You can have the trigger condition to pass only if has Ok (not Warning nor FatalError).
But straight forward method is to find the reason why its giving out error and why the job is not aborting,
But straight forward method is to find the reason why its giving out error and why the job is not aborting,
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 36
- Joined: Wed Aug 09, 2006 12:18 am
- Location: Chennai
Sorry for posting it in the wrong forum.
Kumar,
I cannot go for a sequence for every job since i have almost 60 - 70 jobs.
Ray,
The job keeps on running it doesnt get aborted,even in the designer.
From my perspective,some communication gap between the Teradata Mload and Datastage.
Is that anything i need to do, to fill it up?
Regards,
Kumar,
I cannot go for a sequence for every job since i have almost 60 - 70 jobs.
Ray,
The job keeps on running it doesnt get aborted,even in the designer.
From my perspective,some communication gap between the Teradata Mload and Datastage.
Is that anything i need to do, to fill it up?
Regards,
Sakthi
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
What you see in Director is not the actual status but the last reported status. If the job has failed without being able to update its status to DataStage, it will appear to be running forever. Clear the status file in this case.
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: 36
- Joined: Wed Aug 09, 2006 12:18 am
- Location: Chennai
Ray,
I have cleaned up the resources in director,then also it runs fine for once or twice then again it just keeps on saying it is running where as Mulitload has failed.
Kumar,
This job is already called in an Sequencer even the sequencer keeps on runnnig waiting for the status from the job.
Regards,
I have cleaned up the resources in director,then also it runs fine for once or twice then again it just keeps on saying it is running where as Mulitload has failed.
Kumar,
This job is already called in an Sequencer even the sequencer keeps on runnnig waiting for the status from the job.
Regards,
Sakthi
What you see in log? Do you see the error message from Mload and will it hang just after that?
It may be due to some lock held in database or a response waiting from database.
Do check the background process in database when the job hangs. Also do post the logs that you feel will be useful to analysis.
It may be due to some lock held in database or a response waiting from database.
Do check the background process in database when the job hangs. Also do post the logs that you feel will be useful to analysis.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
-
- Charter Member
- Posts: 47
- Joined: Fri Mar 18, 2005 5:59 am