I am running a job sequence containing 7 parallel jobs. All the 7 jobs are running in parallel. Each job has below design.
Sequence File ---> Transformer ---> DB2 Table(DB2 EE Stage, Load and truncate method)
Sometimes all the individual jobs are in hanged state. The datastage director shows all the jobs in running state but no data is actually getting inserted into underlying table. Then I use to stop all 7 parallel jobs and clear the underlying table from load pending state and re-start the main job sequence.
After doing this, the job sequence runs fine. Need to know why the jobs are getting hanged.
I checked the network traffic, Memory, CPU Utilization, table space etc...Everything is fine.
Don't know why this thing is happening. These jobs are in production and I have executed them more than 100 times so far without any trouble.
You say 'underlying table' singular - are all seven jobs writing to the same table? If not, I would think getting your DBA involved to monitor things when they are 'hung' would be the next logical step.
-craig
"You can never have too many knives" -- Logan Nine Fingers
All 7 jobs are writing to 7 different tables. Cross checked with the DBA, but no activity is going on these 7 tables when the jobs appear in hanged state.
You mention that these jobs are running in production fine. I am assuming that your problem is in other environment. Are the database tablespaces the same in that environment as they are in prod? When DB2 executes load it does some locking at tablespace level.
</a>