Job Aborts with No such Condition error even though condition does exist
search cancel

Job Aborts with No such Condition error even though condition does exist

book

Article ID: 279999

calendar_today

Updated On:

Products

CA Automic Applications Manager (AM)

Issue/Introduction

A Job run may Abort with the below error even though the condition exists:

ErrorMsg: AwE-5001 Database Query Error
Details: null
java.sql.SQLException: ORA-20024: No such Condition 1 on TEST_JOB 
ORA-06512: at "APPWORX.AWAPI2", line 487
ORA-06512: at "APPWORX.AWAPI2", line 460
ORA-06512: at "APPWORX.AWAPI", line 112
ORA-06512: at "APPWORX.AWAPI", line 3295
ORA-06512: at "APPWORX.AW_WEB_API", line 362
ORA-06512: at line 1

Cause

There may be a data inconsistency on the Job condition

Resolution

Deleting and recreating the condition should assist in resolving the issue:

  1. Open Job or Process Flow and delete the condition
  2. Apply/OK to save and close
  3. Reopen the Job or Process Flow, and recreate the condition
  4. Apply/OK to save and close
  5. Rerun Job or Process Flow