a job which used to run normally before is abending now with , following error messages
main_program: Unexpected exit status 1 (...)
5615 FATAL Wed Mar 11 18:59:10 2009
FUNL_Combine,3: Failure during execution of operator logic.
5618 FATAL Wed Mar 11 18:59:10 2009
FUNL_Combine,3: Fatal Error: waitForWriteSignal(): Premature EOF on node resource_server Socket operation on non-socket
5619 FATAL Wed Mar 11 18:59:10 2009
TRNS_Rej_Recs,3: APT_IOPort::receiveAcks(0,force): read on [fd 13: L10.116.174.111:11081, R10.116.174.107:35868] failed - 73 (Connection reset by peer).
5621 FATAL Wed Mar 11 18:59:10 2009
TRNS_Rej_Recs,3: sendWriteSignal() failed on node resource_server ds = 24 conspart = 3 Broken pipe
5625 FATAL Wed Mar 11 18:59:11 2009
FUNL_Bypass_Diff_Status_Dollar_Amt,3: Failure during execution of operator logic.
5628 FATAL Wed Mar 11 18:59:11 2009
FUNL_Bypass_Diff_Status_Dollar_Amt,3: Fatal Error: waitForWriteSignal(): Premature EOF on node resource_server Socket operation on non-socket
5629 FATAL Wed Mar 11 18:59:11 2009
resource_server_node2: APT_PMMP::makeMessage: bad message on port (5,14) - header is {2}
5630 FATAL Wed Mar 11 18:59:11 2009
resource_server_node2: Internal Error: (0):processmgr/msgport.C: 1267: FAILURE: Impossible code statement reached:
5631 FATAL Wed Mar 11 18:59:11 2009
main_program: The Section Leader on node resource_server_node2 has terminated unexpectedly.
the job design is
reading from the db2udb table using db2 ent stage, trnasformation (transformer + funnel + aggregator), finally loading to a already truncated table.
I have searched the forum for all of the error messages but could not find the solution, hence posting again...
any idea/thoughts on how to solve this?
guess it has all the FATAL errors a PX job will have