search cancel

AWA: Orphaned records in the ESTP table: Leftovers after Job deactivation


Article ID: 144264


Updated On:


CA Automic Workload Automation - Automation Engine


Orphaned records in the ESTP table i.e., row in the EH table for the Job is already deleted, but a record in the ESTP table is left back.

The following kind of errors may appear on the WP logs until the ESTP table is cleaned:

20200929/112157.774 -  U00003631 Dump caused by: 
20200929/112157.774 -  U00000002 EXISTS
20200929/112157.774 -  U00011801 Error in Server routine 'JPEXEC_R', Server: 'EUP4#WP008' AE system: 'EUP4'.


To check if the issue is occurring, the following query is useful:

select * from ESTP where estp_AH_idnr not in (select eh.EH_AH_Idnr from EH);


A problem has been fixed where some orphaned records were left in the ESTP table.

By deactivating a job, the Automation Engine did not delete the record of the job from the ESTP Table. This happened sporadically, depending on the order of messages processed by the Automation Engine.


Release : 12.1, 12.2 and 12.3



First, you will need to remove the orphan records from ESTP that appear with the result of the query:

select * from ESTP where estp_AH_idnr not in (select eh.EH_AH_Idnr from eh);


Then, update to a fix version listed below or a newer version if available so that the issue will not reoccur in the future.

Fix version:

Component(s): Automation.Engine

Automation Engine 12.3.2 - available 

Automation Engine 12.2.6 - available 

Automation Engine 12.1.8 - available