U0003516 UCUDB: Affected lines in function 'UPDATE' = '0'

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

After a Workflow is canceled, which has an external dependency it can trigger force traces:

U00011572 JP cancel initiated by ELSE condition of external condition: '123_123_XD'.
U00011503 Workflow '123_567_WF' (RunID '1234567890') ended abnormally.
U00011572 JP cancel initiated by ELSE condition of external condition: '123_567_XD'.
U00011503 Workflow '123_567_WF' (RunID '1234567890') ended abnormally.
U00011572 JP cancel initiated by ELSE condition of external condition: '123_890_XD'.
U00011503 Workflow '123_567_WF' (RunID '1234567890') ended abnormally.
U00003620 Routine 'JPEXEC_R' forces trace because of error.
U00003516 UCUDB: Affected lines in function 'UPDATE' = '0'
U00011801 Error in Server routine 'JPEXEC_R', Server: 'UC4#WP007' AE system: 'UC4'.
U00003516 UCUDB: Affected lines in function 'UPDATE' = '0'
U00015006 System forced memory trace dump.
U00003631 Dump caused by: 
U00003516 UCUDB: Affected lines in function 'UPDATE' = '0'
U00011801 Error in Server routine 'JPEXEC_R', Server: 'UC4#WP007' AE system: 'UC4'.

Environment

Release:
Component: AAUTEN

Cause

In this special circumstance, the deactivation of a workflow (JOBP object) with an external dependency causes the issue. 

The server routine TIMER_DO are trying to delete all e*tables and then tries to update the corresponding EJPP record for the external task but obviously, the record was already deleted. 

Resolution

This error can be ignored - it has no consequences on the Automation Engine as the record has already been deleted.