Hello,
I have a job which hangs when it is kicked off. I can't see much info in the log to see where it is hanging. The job is stuck at this step:
main_program: APT configuration file: /dsinst001/IBM/InformationServer/Server/Configurations/config2x.apt
{
node "node1"
{
fastname "ttstsza8011"
pools ""
resource disk "/dstemp001/is8/Datasets" {pools ""}
resource scratchdisk "/dstemp001/is8/Scratch" {pools ""}
}
node "node2"
{
fastname "ttstsza8011"
pools ""
resource disk "/dstemp001/is8/Datasets" {pools ""}
resource scratchdisk "/dstemp001/is8/Scratch" {pools ""}
}
}
The job is sourcing from an Oracle table and loading another Oracle table. I don't have the privileges to check if there is a table lock. Is there a way to know if it is indeed stuck at the source query or at some other steps?
Cheers!
DataStage job hangs
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Welcome aboard.
That's not a step - it's the log entry containing the configuration file that the job is using.
Clearly the job, being such a simple design, is waiting for *something* in Oracle. Enlist your DBA to learn what that is.
That's not a step - it's the log entry containing the configuration file that the job is using.
Clearly the job, being such a simple design, is waiting for *something* in Oracle. Enlist your DBA to learn what that is.
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: 5
- Joined: Sat Apr 17, 2010 10:56 am
Database hanging
I wondered if you could add a little more to this. I have the same issue, and I agree that this is a database issue. I will be speaking with my DBAs about new indexes. That being said, I would prefer the Datastage job to timeout and fail rather than simply hanging. If it fails we will get notified and we can address the issue. If it hangs, we don't know anything is wrong until someone realizes the job didn't finish. Are there any settings we could check to cause the job to timeout and fail rather than hanging?
Grant Dever
Programmer Analyst Sr
Programmer Analyst Sr