Parallel job getting failed

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
abbhi
Participant
Posts: 32
Joined: Thu May 08, 2014 6:34 pm

Parallel job getting failed

Post by abbhi »

Hi,

I am getting below error in one of my parallel job.
This job is schedule to run every 8 hours and it only fails in its 1st run.
However when we compile the job and then run manually it finish successfully.

The error is below:

JVMDUMP006I Processing dump event "abort", detail "" - please wait.
JVMDUMP032I JVM requested System dump using '/DSProjects/Projects/Project1/core.20121203.180210.28311774.0001.dmp' in response to an event
Note: "Enable full CORE dump" in smit is set to FALSE and as a result there will be limited threading information in core file.
JVMDUMP010I System dump written to /DSProjects/Projects/Project1/core.20121203.180210.28311774.0001.dmp
JVMDUMP032I JVM requested Java dump using '/DSProjects/Projects/Project1/javacore.20121203.180210.28311774.0002.txt' in response to an event
JVMDUMP010I Java dump written to /DSProjects/Projects/Project1/javacore.20121203.180210.28311774.0002.txt
JVMDUMP032I JVM requested Snap dump using '/DSProjects/Projects/Project1/Snap.20121203.180210.28311774.0003.trc' in response to an event
JVMDUMP010I Snap dump written to /DSProjects/Projects/Project1/Snap.20121203.180210.28311774.0003.trc
JVMDUMP013I Processed dump event "abort", detail "".

Parallel job reports failure (code 256).

We don't get this error in other run of this job. This is a bulk load job.
Is it could be because in morning run of the job ie the first run where it fails it process huge amount of data and it other runs it not.
Please advice?

Thanks,
Abhishek
priyadarshikunal
Premium Member
Premium Member
Posts: 1735
Joined: Thu Mar 01, 2007 5:44 am
Location: Troy, MI

Post by priyadarshikunal »

http://www-01.ibm.com/support/docview.w ... wg21593545

Check this link and see if this helps. There are many threads on this error with different configuration issues causing the same error, please do a search and check if any of those help.

Do you have anything else running on that server that uses java which might be changing the path permanently instead of for their session only and has a run scheduled during that time?

What kind of database you have? are there any other error or warning messages? do you get anything in the log like "From previous run" when you reset the job?
Priyadarshi Kunal

Genius may have its limitations, but stupidity is not thus handicapped. :wink:
Post Reply