Sudden growth in AutoSys Database Size

Document ID : KB000116823
Last Modified Date : 11/10/2018
Show Technical Document Details
Issue:
The size of the for Autosys database almost doubled over a period of 1-2 months.
What things should be looked at to determine why?
 
Environment:
Product - Workload Automation AE 11.3.x
Platform - Linux/Unix, Windows
Database - Oracle, Sybase, SQL
 
Resolution:
Review $AUTOUSER/out/DBMaint.out to confirm the database maintenance is occurring.
DBMaint will purge older records from the database, opening up space for new entries.
To adjust DBMaint settings modify the $AUTOUSERV/bin/DBMaint file's archive_events settings.

Examine $AUTOUSER/out/event_demon.$ATUOSERV log files to see if more jobs/events have been processed per day than prior days.
Run the autoaggar command to review the number of events, alarm, runs etc.. per day or month to see if it has been increasing steadily or spiked.
Confirm that the aedbadmin and autosys database user are not also the owner of user created objects.
Query the ujo tables to identify the large ones to see if there is a problem with old records not being archived.
Common tables to check:
ujo_alarm
ujo_audit_info
ujo_audit_msg
ujo_chase
ujo_event
ujo_job
ujo_job_runs
ujo_proc_event