Parallel job reports failure (code 139)
Posted: Tue Sep 02, 2014 12:12 am
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..
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..