Update Aggregated job gets stuck in Processing after spinning off a second instance

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Update Hierarchy Data job gets stuck in Processing and creates jobs bottleneck. Second instance will start with same exact timestamp and complete.

Processing Job is in CMN_SCH_JOBS and CMN_JOB_SCH_RUNS but not in CMN_SCH_JOB_CURR_RUNS.

Error Exception due to DB Connection failure08006 in BG logs

 

STEPS TO REPRODUCE:

1. Schedule Update Aggregated job to run regularly on your environment

Expected Results: The Update Aggregated job to run consistently and to be either in Failed or Completed status. If there is an error, job should be marked as Failed

Actual Results:  Once in a while the job will get stuck in Processing, a second instance is getting span off that completes successfully with the same timestamp. All other incompatible jobs will be queued up

Environment

Clarity 16.2.3.2

Cause

DE176444

Resolution

Fixed in

• Clarity 16.4.1
• Clarity 16.3.3 Patch 3 (16.3.3.3)
• Clarity 16.4.0 Patch 1 (16.4.0.1)

Workaround: Restart BG, ensure the job is no longer Processing.