Hi All,
I am facing a strange problem in some of my jobs. Sometimes whenever i trigger my DataStage job it shows as running in the director logs and on OS side too but when you see the detail logs then you will find it is hung.
I tried restarting my DataStage services but still same issue is coming and also this is intermittent.
Let me know if someone has some thoughts to fix this issue.
Datastage job gets into hung state. (Parallel job initiated)
Moderators: chulett, rschirm, roy
-
rohitagarwal15
- Participant
- Posts: 102
- Joined: Thu Sep 17, 2009 1:23 am
-
stephan.zahariev
- Premium Member
- Posts: 9
- Joined: Sun Feb 12, 2012 11:05 am
- Contact:
Hi,
Do you have grid enabled? This hang could be due to the scheduling software is unable to find a free node to run your job.
If this is not the case, then you will need to have a closer look at the director log messages (including warning and information) to get a clue about the potential problem.
But what you have described could be tricky to find.
Do you have grid enabled? This hang could be due to the scheduling software is unable to find a free node to run your job.
If this is not the case, then you will need to have a closer look at the director log messages (including warning and information) to get a clue about the potential problem.
But what you have described could be tricky to find.
Stephan
http://szahariev.blogspot.com
http://szahariev.blogspot.com
There are so many possible causes for this type of situation that no qualified help can be forthcoming without additional information from your side. Here are just a few to start off with:
Where is it hanging according to the detail log?
Are you doing SELECTs with non-default transaction levels?
Are you doing WRITEs which might be blocking or blocked at the database level?
Are you even accessing a database and, if so, which one and how are you accessing it?
What additional messages are in the log when you kill the job from Director?
Where is it hanging according to the detail log?
Are you doing SELECTs with non-default transaction levels?
Are you doing WRITEs which might be blocking or blocked at the database level?
Are you even accessing a database and, if so, which one and how are you accessing it?
What additional messages are in the log when you kill the job from Director?
</a>-
rohitagarwal15
- Participant
- Posts: 102
- Joined: Thu Sep 17, 2009 1:23 am
Thanks for the reply. Please find below details as requested.
1) There is no grid server. This is standalone server.
2) In job log only 4 entries are coming for that run - User defined variables, Adding message handler, environment variable adding and last it shows Parallel job initiated and then if we do right click and monitor the job it shows it in ready state.
3) We are using Oracle 11g database.
4) We are reading the data from database and writing to dataset.
1) There is no grid server. This is standalone server.
2) In job log only 4 entries are coming for that run - User defined variables, Adding message handler, environment variable adding and last it shows Parallel job initiated and then if we do right click and monitor the job it shows it in ready state.
3) We are using Oracle 11g database.
4) We are reading the data from database and writing to dataset.
Rohit
-
priyadarshikunal
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
