High system utilization - Cleanup of LASLM

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

We are observing high system utilization of our prod environment.

We had issues earlier and performed a cold start, however the system utilization is spiking.

We found a query that appears into the DB AWR related to LASLM table. This particular table as per the schema is used for SLO objects.

However we are not using any SLOs around 6 months now. 

Currently we have more than 115M records in this table.

Environment

Release : 12.3 and v21

Component : AUTOMATION ENGINE

Cause

LASLM is not maintained by the Reorg/Unload Utility

Resolution

The LASLM tables need to be maintained externally.

Resolution:
The statement

delete from LASLM where LASLM_AH_Idnr not in (select AH_Idnr from AH);

should remove all records from LASLM which are not referenced to an AH record.
If the customer would prefer to consider only historical data, please take LASLM_Date into account.

 

Additional Information

There is no downtime required for this activity but it may affect operations.

Please note that when you are modifying a production database, you should always take a backup of the database first.