Application(s) stuck in Processing

book

Article ID: 7217

calendar_today

Updated On:

Products

DSERIES- SERVER CA Workload Automation DE - System Agent (dSeries)

Issue/Introduction

The database believes that an application or applications are in a Processing state, where in fact they are not. This in turn causes those Applications with "Do not trigger if active" selected, to not trigger.

Cause

Cause is unknown.

Environment

Workload Automation DE r11.3.x, r12.x

Resolution

Before performing the below procedures, you should open a case with CA Support to record the occurrence of the experienced behavior and obtain permission to proceed. 

  1. Using the Desktop Client, review and notate the Applications and their respective Generation numbers that are impacted by the described behavior.
  2. After composing a listing of those application and generation numbers, execute the SQL query: select STATUS from ESP_WSS_APPL where APPL_NAME like '<name>' and APPL_GEN_NO=<number>;
  3. If the status of the application displayed is anything other than 2, then you can update the database to mark the application as complete. STATUS of 2 is complete.
  4. You should work with your DBA to get the necessary records updated according to your listing of applications/generation numbers. An example of SQL statement to update a record would be update ESP_WSS_APPL set STATUS=2 where APPL_NAME='XYZ' and APPL_GEN_NO=45. This is only an example for reference purposes only. 
  5. Note: In some cases it will be necessary to perform similar actions to the ESP_RTWOB table.
  6. Once this is done, you can either manually execute the PURGECOMPLETEDJOBS command from the CLI perspective for all specific application generations by entering the command PURGECOMPLETEDJOBS application("XYZ") or allow your scheduled HOUSEKEEPING process to clear them out according to your organizations retention standards.