Page 1 of 1

DataStage job hangs

Posted: Sat Apr 17, 2010 11:19 am
by new_dsuser
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!

Posted: Sat Apr 17, 2010 4:09 pm
by ray.wurlod
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.

Posted: Sun Apr 18, 2010 9:55 am
by new_dsuser
Thanks Ray. I tuned the query a bit and it's running fine now. Thanks again.

Database hanging

Posted: Mon Jul 18, 2011 6:37 am
by devo
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?