Hi,
I went through all the related posts , which give me a understanding that the Parallel job reports failure (code 139) is more sort of generic message and there could be many reason for the error . However in my case am not getting other message like core dump / Segementation fault etc.
There is absolutly no other information in the log ...
We have 3 seq jobs each having 5 extract jobs (in total 15 jobs) which reads from oracle table and writes to file . The abort happens randomly on any job and works fine on restart.
Is there any variable which can help me Debug and pin point this issue ...
Since this is production system , would like to have a concrete thing before making any change..
Parallel job reports failure (code 139)
Moderators: chulett, rschirm, roy
Re: Parallel job reports failure (code 139)
These are the two confifuration parameters , which has been recommneded by others to change..
APT_MONITOR_SIZE = 50000
APT_MONITOR_TIME = 10
APT_MONITOR_SIZE = 50000
APT_MONITOR_TIME = 10
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
try this link.
Also, it may relate to segmentation faults or some other issue. Do you get anything when you reset the aborted job? something like "From previous run"
Also, it may relate to segmentation faults or some other issue. Do you get anything when you reset the aborted job? something like "From previous run"
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.
Genius may have its limitations, but stupidity is not thus handicapped.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI