Orphan entries in BH/BT tables

Products

• CA Automic One Automation

Issue/Introduction

Due to an incomplete UC4 script, in some cases, orphan entries are left in the BH/BT table.

This can lead to a sizeable number of rows in the tables BH and BT.

In some cases, where the variables set by PUT_READ_BUFFER are not defined in the follow-up Task that reads the variables, a warning message is displayed and the Task is not started.

So far 3 cases have been identified that leave orphan entries:

• PUT_READ_BUFFER is used but no ACTIVATE_UC_OBJECT follows in the UC4 script
• ACTIVATE_UC_OBJECT calls a non-existing Object
• Activation of a non-existing CALL or any object from JOBP in Task Evaluation (An error is displayed but BH/BT are not cleaned)

 

Cause

This is caused by PUT_READ_BUFFER when follow-up Tasks are incoherent. In other words, if the data stored by PUT_READ_BUFFER is not consumed.

Resolution

Solution:

Ensure that scripts using PUT_READ_BUFFER are followed up by a Task that consumes that data in the buffer.

 

Solution:

A code fix is provided that adds the cleanup of BH/BT to the Cold Start procedure, so these tables can be cleaned up if needed.

 

To use this, please update to a fix version listed below or a newer version if available.

Fix version:

Component(s): Automation Engine

Automation.Engine 21.0.10 - Available

Automation.Engine 24.1.0 - Planned release June 2024

Additional Information

This is the reference for the fix: AE-32019