Integration Avaloq - KILL JOB Fails with ORA-01403: no data found when wildcards are used in Job Name

Products

• CA Automic Workload Automation - Automation Engine
• Automic SaaS
• CA Automic One Automation

Issue/Introduction

The KILL JOB does not  work if wildcards are specified within the Job name.

Ex: JOB1%

It works if the full name of the job is used 

Ex: JOB123456890

Expected Behavior: As per documentation the use of Oracle wildcards are valid

In the Kill Avaloq Job section, you define the parameters relevant to run that job on the Avaloq system from Automic Automation:

• Avaloq Job Name

  Enter the name of the job that you are targeting on Avaloq. You can use Oracle wildcards.

Actual Behavior: The job fails and the a trace file is generated with the error ORA-01403: no data found

20250610/140615.507 - 98     ----------------------- Stack Trace -----------------------
20250610/140615.510 - 98     com.automic.ra.agent.RaJobException: Job not found: java.sql.SQLException: ORA-01403: no data found

Environment

Release: 21.x 24.x 

Component: Integration Avaloq

Cause

DE171673

Resolution

Update to a fix version listed below or a newer version if available.

Fix version:

Component(s): Integration Avaloq

Integration Avaloq 21.0.3 -  Available

Integration Avaloq 24.0.1 - Available

Additional Information

Public Description: A problem has been fixed when killing/canceling a job in Avaloq