12.0 LAH data found in 12.3 LAH table

book

Article ID: 225937

calendar_today

Updated On:

Products

CA Automic One Automation

Issue/Introduction

While looking at the LAH table, found a lot of old entries that don't seem to fit the normal pattern for version 12.3.6.  Questions:

How can these be deleted?
Can these affect telemetry performance?

Steps to reproduce:
Find a 12.0 system with LAH records.  They will look something like:

LAH_System LAH_Date LAH_Type LAH_Name LAH_Platform LAH_Hardware LAH_LicClassUsed LAH_LicCategory LAH_Restriction LAH_LicClassNec LAH_Checksum LAH_Count1 LAH_Count2 LAH_Count3 LAH_Count4 LAH_Count5
UC4 202012 SRV CP SRV.WIN WINDOWS W Production NULL NULL NULL 1 0 0 0 0
UC4 202012 SRV WP SRV.WIN WINDOWS W Production NULL NULL NULL 1 0 0 0 0
AUT1207 202108 SRV CP SRV.WIN WINDOWS W Production NULL NULL NULL 1 0 0 0 0
AUT1207 202108 SRV WP SRV.WIN WINDOWS W Production NULL NULL NULL 1 0 0 0 0
AUT1207 202108 USER DC JAVA JAVA 0 JAVA NULL NULL NULL 1 1 0 0 0
AUT1207 202109 SRV CP SRV.WIN WINDOWS W Production NULL NULL NULL 3 0 0 0 0
AUT1207 202109 SRV WP SRV.WIN WINDOWS W Production NULL NULL NULL 6 0 0 0 0
AUT1207 202109 USER DC JAVA JAVA 0 JAVA NULL NULL NULL 1 1 0 0 0
AUT1207 202110 SRV CP SRV.WIN WINDOWS W Production NULL NULL NULL 1 0 0 0 0
AUT1207 202110 SRV WP SRV.WIN WINDOWS W Production NULL NULL NULL 1 0 0 0 0

Upgrade system to 12.3, wait 24 hours for LAH to start putting in records for telemetry.
Look at the records in the LAH table

Expected behavior: only 12.3 data should be in the LAH table.

Actual behavior:
data shows the 12.0 data seen above plus 12.3 data

LAH_System LAH_Date LAH_Type LAH_Name LAH_Platform LAH_Hardware LAH_LicClassUsed LAH_LicCategory LAH_Restriction LAH_LicClassNec LAH_Checksum LAH_Count1 LAH_Count2 LAH_Count3 LAH_Count4 LAH_Count5
AWA 211005 235959 high_availability_cluster 0       NULL NULL NULL 0 NULL NULL NULL NULL
AWA 211005 235959 maximum_active_app_nodes 0       NULL NULL NULL 0 NULL NULL NULL NULL
AWA 211005 235959 maximum_active_mainframe_nodes 0       NULL NULL NULL 0 NULL NULL NULL NULL
AWA 211005 235959 maximum_active_tech_nodes 0       NULL NULL NULL 0 NULL NULL NULL NULL
AWATE 211005 235959 high_availability_cluster 0       NULL NULL NULL 0 NULL NULL NULL NULL
AWATE 211005 235959 number_of_executions 0       NULL NULL NULL 0 NULL NULL NULL NULL
BOND 211005 235959 high_availability_cluster 0       NULL NULL NULL 0 NULL NULL NULL NULL
AAAI 211005 235959 maximum_active_app_nodes 0       NULL NULL NULL 0 NULL NULL NULL NULL
AAAI 211005 235959 maximum_active_mainframe_nodes 0       NULL NULL NULL 0 NULL NULL NULL NULL
AAAI 211005 235959 maximum_active_tech_nodes 0       NULL NULL NULL 0 NULL NULL NULL NULL
ASO 211005 235959 high_availability_cluster 0       NULL NULL NULL 0 NULL NULL NULL NULL
ASO 211005 235959 number_of_orchestrated_systems 0       NULL NULL NULL 0 NULL NULL NULL NULL

 

 

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Resolution

It is as designed for records originally in 12.0 in the LAH table to still be in the LAH table in 12.3.  These will automatically be purged when their timestamp hits ~12 months.  The delete statement that is run daily deletes all LAH records with a LAH_Date less than 12 months ago.  There should be no impact to performance.