Name	Points
Greg Moeller	4184
David Williams	3349
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1377
Roger French	1315
mark.cook	1244
Chris Martin	825

What determines whether a node error causes a workunit to fail?

1 Replies

0 Subscribed to this topic

53 Subscribed to this forum

Sort:

Author

Messages

Woozy

Veteran Member

Posts: 709

New Poster

8/17/2011 8:58 PM

We are experiencing a problem with our PFI server that is causing S3 queries to have a connection failure (which we're working with Lawson to resolve). However, this is causing a symptom that is odd to me.

For some reason, we have some flows where the workunit goes into a status "3-Processing Failed" when the error occurs, but other flows (with the same error) where the workunit completes with a status of "4-Processing Completed" after the error occurs.

Can anyone explain why two identical errors would result in different workunit status values?

Thanks! Kelly

Rob Conrad

Veteran Member

Posts: 73

New Poster

8/19/2011 4:33 PM

Hi Woozy -

I've seen this before with a DB2 / AIX client. Check with your DB2 DBA regarding optimistic vs. pessimistic concurrency in DB2.

You might have some record locking issues in DB2 and this is what could cause the intermittent failures. This was a real pain to troubleshoot, but root cause ended up being a row lock vs. a table lock in DB2 and once the DBA changed the locking properties the issue was resolved.

RC