Deployment Guide › iConsole Standard Searches, Reports and Policies › Dashboard Data Aggregation › Reschedule Initial Aggregation For Older Events

Reschedule Initial Aggregation For Older Events

When you upgrade an iConsole dashboard to the current CA DLP version, or if you install a new dashboard and need to aggregate your existing events, be aware that older event data may not be included in the dashboard charts and metrics until the day after the dashboard installation or upgrade.

If your aggregated data includes over 100,000 data events, events more than two months old will not be included in the dashboard until the day after the installation or upgrade. This is because the initial aggregation job for this older data is configured to run during an off-peak window to avoid impacting system performance during office hours. By default, this off-peak window starts at midnight (CMS time) and lasts 300 minutes until 5am, but you can reconfigure it to run when you want.

To reschedule the initial aggregation for older events

Run the following SQL commands to reschedule the off-peak window for the initial aggregation of older events. In each case, you must be logged onto the CMS database as the primary user. This is the account that CA DLP uses to access the CMS database.

SQL Server CMSs

Run this command:

EXEC WgnDW_Configure_DW 
 @offpeak_run_starttime_hour = <hour>, 
 @offpeak_run_timeout_mins = <window>  

Where:

<hour> specifies the starting hour. It can be any value from 0 to 23. For example, 0 specifies a midnight start; 23 specifies an 11 pm start.

<window> specifies the window duration (in minutes) for the aggregation job. For example, set this to 240 to specify a four hour window.

Oracle CMSs

Run this command:

BEGIN
  WgnDW_Configure_DW( 
    offpeak_run_starttime_hour => <hour>, 
    offpeak_run_timeout_mins => <window> 
  );
END;

Where <hour> and <window> are as described above.

To disable the initial aggregation for older events

Run the above commands, but set <window> to -1. This disables off-peak processing. This may be useful, for example, to disable processing Monday through Friday but re-enable it over the weekend. For example, on a SQL Server CMS, run this command:

EXEC WgnDW_Configure_DW 
 @offpeak_run_starttime_hour = 0, 
 @offpeak_run_timeout_mins = -1