The most recent past month's historical performance statistics are missing when running or viewing the autoaggr report.
AutoSys Workload Automation AE (All Platforms)
The AutoSys scheduler natively initiates the aggregation of monthly performance data automatically at the transition into a new calendar month. If the AutoSys scheduler is down, or if it encounters a critical database connectivity issue during this specific window, the background aggregation task fails to initiate, leaving the monthly statistics unpopulated.
Check the scheduler's log file for the first day of the new month to verify if the product was active and attempted to generate the prior month's statistics.
Review the following log file: $AUTOUSER/out/event_demon.$AUTOSERV.<MMDDYYYY> (Where <MMDDYYYY> corresponds to the first day of the new month).
Look for any communication or database errors that may have intercepted the scheduler's connection. For example, Oracle connection errors like the following will prevent data aggregation:
[05/31/2026 23:57:58] CAUAJM_E_18402 ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
[05/31/2026 23:57:58] CAUAJM_E_10649 Server example.com was not available during connection operation.
[05/31/2026 23:58:58] CAUAJM_E_18407 Failed to connect to Oracle server: example.com
[05/31/2026 23:58:58] CAUAJM_E_18400 An error has occurred while interfacing with ORACLE.
[05/31/2026 23:58:58] CAUAJM_E_18401 Function <Olog> invoked from <openProc> failed at <163>
If the automated run was skipped or failed due to database unavailability, you can manually trigger the aggregation mechanism using the sendevent command line interface.
From an AutoSys command prompt, execute the following command:
sendevent -E AGGREGATE -l MONTHLY
Run your autoaggr command again to confirm that the expected monthly statistics are now present.
To track processing details or catch potential runtime issues during manual execution, monitor the aggregator log file: $AUTOUSER/out/aggregator.$AUTOSERV