After Cancel Pending Uproc its Class Event remains owls_class_event_select error

Products

• CA Automic Dollar Universe

Issue/Introduction

When using Incompatibility Classes inside Uprocs there is an issue in case a Uproc in status Pending is Cancelled:
The Class Event is created right when the Uproc goes from status "Launch Wait" to "Pending"
Cancelling the Pending Uproc does NOT delete the previously created Class Event, so it may provoke that all other Uprocs using this Incompatibility Class remain forever in status Event Wait.

In the History Trace we can see something like:

Incompatibility Cond. 001 for class <CLASS_NAME>
Session: <SESSION_NAME> Uproc: <UPROC_NAME> M.U.: <MU_NAME>

When trying to delete via UVC the impacted Class Event, it fails with the following error and the Class Event is not removed:

On environment [COMPANY/NODE/AREA]:
DUAS: Class Event List on COMPANY for NODE in Area AREA:
owls_class_event_select error: 11

Environment

Release : 6.x
Component : DOLLAR UNIVERSE

 

Cause

Defect

Resolution

Solution:

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

Fix version(s): 
Component: Dollar.Universe.Application.Server
Dollar Universe 6.10.41

Workaround 1:

Upgrade the Node and UVC to version 6.9.41 or superior and delete manually the Class Event using UVC, go to the menu Monitoring - Class Events, delete manually the impacted Class Event.

Workaround 2:

If the Node can't be upgraded, you will need to reinitialize the Class Event data file of the concerned area (A or S or I or X) while the node is stopped:

uxrazfic u_fmlc60 AREA

Additional Information

Some other scenarios where this issue i.e. Class Event remained and not being cleared automatically

1: Issue at Operating system level like disgraceful crash etc. which caused I/O interruption and above issue is observed.

Note:

In case if the jobs awaiting for some Class Event remain in Event Wait and not execute automatically after having Deleted the awaited Class Event, the Dollar Universe Administrators should force these jobs to status Time overrun by setting an End date in the past and click on Run, after that these jobs should be rerun and they should run fine.