Job finished succesfully with fatal error

soumya5891 · Post by **soumya5891** » Thu Oct 27, 2011 7:48 am

I have a parallel job with the following design

Dataset----->surrogatekey------>target DB2 table

I am using DB sequence as surrogate key generator.The user with which the job ran was not access to the particular DB sequence.So the job got fatal error.But instead of aborting the job it has been finished with warning.

chulett · Post by **chulett** » Thu Oct 27, 2011 8:05 am

We've seen this posted before - fatal in the log, job doesn't abort - but I don't recall ever seeing a good reason for it. Me, I'd ping your official support provider and let us know what they say.

eph · Post by **eph** » Fri Oct 28, 2011 8:55 am

For information,

I get the same kind of behavior using an Oracle Enterprise to retrieve data (getting a "table or view does not exists"), and the job abort in some cases, but mostly continues and finish, even with this "Fatal" error.

Eric

soumya5891 · Post by **soumya5891** » Wed Nov 02, 2011 10:43 am

Is there extra patch that needs to be installed to avoid this situation

chulett · Post by **chulett** » Wed Nov 02, 2011 10:45 am

Again... official support provider.

ray.wurlod · Post by **ray.wurlod** » Wed Nov 02, 2011 6:37 pm

What's really needed is a change in mindset. In server jobs a Fatal error always causes the job to abort. In parallel jobs this is not necessarily the case - the controlling process (section leader or conductor) makes a decision about whether the other players, other nodes, can continue to execute.