Multi-thread jobs do not fail if 1 thread ends with error

Document ID : KB000120000
Last Modified Date : 13/11/2018
Show Technical Document Details
Issue:
Oracle Retail Jobs using multi-thread does not fail if one of the threads ended with error.

The log shows Thread 2 ended OK and Thread 1 failed, but the job still ended OK in Automic Workload Automation (AWA):
2018-11-04 13:23:46 RetailThread:1:Waiting for process 
2018-11-04 13:23:46 RetailThread:2:Waiting for process 
2018-11-04 13:24:16 
2018-11-04 13:24:16 Thread RetailThread:2 done 
2018-11-04 13:24:16 Command:/oretail/apprms/retail_home/oracle/proc/bin/salweek rmsb/<orPass>@/@dsRMSAlias 
2018-11-04 13:24:16 Exit code:0 
2018-11-04 13:24:46 Done with all Threads - (2) 
2018-11-04 13:24:46 Progam: salweek : Started: Nov-04-018 12:11:48: Finished : : Thread 1 - aborted in final 
2018-11-04 13:24:46 Progam: salweek : Started: Nov-04-018 12:11:48: Finished : Nov-04-018 12:11:48 : Thread 2 - completed 
2018-11-04 13:24:46 There were errors on execution of the following program threads. 
2018-11-04 13:24:46 
2018-11-04 13:24:46 Thread:RetailThread:1 
2018-11-04 13:24:46 Command:/oretail/apprms/retail_home/oracle/proc/bin/salweek rmsb/<orPass>@/@dsRMSAlias 
2018-11-04 13:24:46 Exit code:255 
2018-11-04 13:24:46 There were errors when executing program thread 
2018-11-04 13:24:46 Searching for daily log. 
2018-11-04 13:24:46 Register daily log:/oretail/apprms/retail_home/log/Nov_04.log 
2018-11-04 13:24:46 Searching for error files. 

EXPECTED:  If one of the threads fail, then the Job should fail too.
Cause:
The RA Oracle multi-thread job is actually behaving as designed.  Instead, the issue is with how the workflow is configured.  The workflow continues to process even though the RA multi-thread job failed.
Resolution:
Use a filter to check for non-zero return codes.