Job Aborts due to "jobid has changed" and "Error 3 setting job to RUNNING status" errors

Products

CA Automic Applications Manager (AM)

Issue/Introduction

After upgrading Applications Manager, specific Jobs may go into Aborted status due to the errors "jobid has changed" and "Error 3 setting job to RUNNING status".

Below is an example of Job's output with the highlighted errors in red:

ERROR -999 ORA-20094: Jobid 123456789.00(123456789.01) jobid has changed
ORA-06512: at "APPWORX.AW4", line 344
ORA-06512: at line 1
ORA-06512: at "APPWORX.AWDYN", line 23
ORA-06512: at line 1

awdyn.execute_plsql
0 SQL: IN:VARCHAR2:java.lang.String: declare so_jobid varchar2(16):='123456789.00'; so_status number:='31'; so_job_pid varchar2(10):='34567890'; so_seq_no number:='234567890'; begin aw4.upd_jq (so_jobid,so_status,so_job_pid,so_seq_no); end;
1 RESULT: OUT:VARCHAR2::nullError on command: awexe UPD_JQ so_jobid=123456789.00 so_status=31 so_job_pid=34567890 so_seq_no=234567890.
Checking to see if awapi is working
Awapi is working.
Attempting to re-execute command
awexe UPD_JQ so_jobid=123456789.00 so_status=31 so_job_pid=34567890 so_seq_no=234567890
ERROR -999 ORA-20094: Jobid 123456789.00(123456789.01) jobid has changed
ORA-06512: at "APPWORX.AW4", line 344
ORA-06512: at line 1
ORA-06512: at "APPWORX.AWDYN", line 23
ORA-06512: at line 1

awdyn.execute_plsql
0 SQL: IN:VARCHAR2:java.lang.String: declare so_jobid varchar2(16):='123456789.00'; so_status number:='31'; so_job_pid varchar2(10):='34567890'; so_seq_no number:='234567890'; begin aw4.upd_jq (so_jobid,so_status,so_job_pid,so_seq_no); end;
1 RESULT: OUT:VARCHAR2::null

Retry failed.
awexe UPD_JQ so_jobid=123456789.00 so_status=31 so_job_pid=34567890 so_seq_no=234567890
Error 3 setting job to RUNNING status

While the above errors can be due to multiple causes, one reason this may occur is an error in the User that is requesting the Job.

If the User requesting the Job has a "Last Name/Description" value containing a space AND is not surrounded by double quote in User's object definition, the above error is triggered.

Environment

Component : APPLICATIONS MANAGER

Cause

In previous versions of Applications Manager, likely version 8.x and below, it was found that if a User's 'Last Name/Description' value contained a space between the value, it would result in unexpected behaviors.

To fix this issue in a later version of Applications Manager, any value containing a space in between the 'Last Name/Description' value would be auto encapsulated with double quotes (ie "Dev User") upon selecting Apply/OK.

Due to a 30 character limit on the 'Last Name/Description' field value, a 'Last Name/Description' value containing a space in between must be shortened to 28 characters since the auto encapsulation of double quotes brings the character count to 30.

This article's error can be seen when the following requirements are met:

Running a version of Applications Manager where 'double quote auto encapsulation' on the 'Last Name/Description' field was not introduced
Have an existing User object whose 'Last Name/Description' value contains 29 or 30 characters which included a space in between the value
Upgrading Applications Manager to a version where 'double quote auto encapsulation' rule exists

When the above requirements are met, the 'double quote auto encapsulation' rule can not be applied to the User during upgrade as the extra double quotes will increase the current character count of the 'Last Name/Description' value from 29 or 30 to 31 or 32.

This creates a configuration where the User's 'Last Name/Description' value is missing it's double quotes even though its value contained a space in the value, which results in this article's erroneous behavior

Resolution

Edit the User object that is assigned as the Requestor of the Aborted Job.
Shorten the 'Last Name/Description' value to 28 character or less if retaining a space in the value or 30 characters if removing the space in the value
Apply/Ok