UC4 WP-Server process keep on failing and restarted.

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation

Issue/Introduction

All WP-Server process keep on failing and restarting. Causing AWI client's connection to break. 

After I restarted entire Automic Engine,Could see  below message on Linux putty screen:

*** buffer overflow detected ***: /opt/automic/server/bin/ucsrvwp terminated
*** buffer overflow detected ***: /opt/automic/server/bin/ucsrvwp terminated
*** buffer overflow detected ***: /opt/automic/server/bin/ucsrvwp terminated
*** buffer overflow detected ***: /opt/automic/server/bin/ucsrvwp terminated
*** buffer overflow detected ***: /opt/automic/server/bin/ucsrvwp terminated

Below are one of the WP-Server logs:
20221115/105535.431 - 26     U00003524 UCUDB: ===> Time critical DB call!       OPC: 'SLCT' time: '1553ms'
20221115/105535.431 - 26     U00003525 UCUDB: ===> 'SELECT PMMA_Idnr FROM PMMA WHERE PMMA_Timestamp <= ? ORDER BY PMMA_Timestamp'
20221115/105537.743 - 26     U00005906 Removed entries from performance tables (PMMA/PMIA/PMIAM/PMMAV): 35328/0/0/4917
20221115/105537.743 - 26     U00003434 Server routine  'MetricsCleanupTask/TIMER' required '0' minutes and '3' seconds for processing.
20221115/105820.494 - 34     U00045075 A task query has been started with the following parameters: Statistics 'N', Status within parent 'N', L
imit '5001'
20221115/105820.712 - 34     U00045076 The task query returned '5001' results in '218' milliseconds.
20221115/105821.020 - 34     U00045075 A task query has been started with the following parameters: Statistics 'N', Status within parent 'N', L
imit '5001'

Environment

Release: 21.X

Cause

BUG

Resolution

This issue is identified as a BUG in Automation Engine and  the solution is to upgrade to 21.0.5

Workaround:

Run the below 2 queries in your Database and check the output of these below queries.

-- check how many wrong records are within AH:
select count(*) from ah where  (AH_TIMESTAMP4 < AH_TIMESTAMP1 OR AH_TIMESTAMP4 < AH_TIMESTAMP2)  and AH_STATUS >= 1800;

-- check if the object type/status is always the same:
select count(*), ah_client, ah_otype, ah_status from ah where  (AH_TIMESTAMP4 < AH_TIMESTAMP1 OR AH_TIMESTAMP4 < AH_TIMESTAMP2) and AH_STATUS >= 1800 group by ah_client, ah_otype, ah_status; 

If the result of no of rows in the output is 0

Then run the below update query to fix the issue.

update ah set ah_timestamp4 = sysdate where (AH_TIMESTAMP4 < AH_TIMESTAMP1 OR AH_TIMESTAMP4 < AH_TIMESTAMP2)  and AH_STATUS >= 1800;
commit; 

If the result of no of rows in the output is not 0, then kindly upgrade to the fixed version