Excessive deadlocks against the EJPOV table cause system slowness and WP utilization to go to 100%

book

Article ID: 87621

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION

Issue/Introduction

Error Message :
DEADLOCK

During normal usage, the system may experience periods of time where WP utilization increases and the system begins to perform slower. Review of the logs shows multiple DEADLOCK messages, often referencing the EJPOV or EJPPO tables similar to:

20161129/134018.271 - U00000006 DEADLOCK
20161129/134018.271 - U00003594 UCUDB Ret: '6' opcode: 'EXEC' SQL Stmnt: 'DELETE FROM EJPPO WHERE EJPPO_AH_Idnr = ?'
20161129/134018.271 - U00003524 UCUDB: ===> Time critical DB call!       OPC: 'EXEC' time: '3:502.407.499'
20161129/134018.271 - U00003525 UCUDB: ===> 'DELETE FROM EJPPO WHERE EJPPO_AH_Idnr = ?'
20161129/134018.287 - U00000006 DEADLOCK


Further review by the DBA may show the deadlock request referencing itself in a Page Lock. 

Cause

Cause type:
Defect
Root Cause: This can be caused by a timing issue during deactivation of a task.

Environment

Release: AUTWAB99000-11.0-Automic Workload Automation-Base Edition
Component:

Resolution

This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.

Fix Status: Released

Fix Version(s):
Automation Engine 11.2.3 - Available

Additional Information

Workaround :
N/A