Platform Deployment Guide › Data Warehouse › Default Configuration for Data Warehousing Jobs › Reschedule the Initial Off-Peak Jobs

Reschedule the Initial Off-Peak Jobs

If you have an existing CMS database that is already populated with a backlog of captured events, events older than two months are not added to the data warehouse until the day after you install the data warehouse.

Why is this? By default, CA DLP processes events less than two months old as soon as possible after the data warehouse is installed. CA DLP then processes events older than two months by running daily off-peak data warehousing jobs. These off-peak jobs run at midnight for 300 minutes.

This default scheduling means that any reports that query the data warehouse, or any charts or tables in the iConsole dashboard, may contain incomplete data until all relevant event data has been added to the data warehouse.

But you can circumvent this problem by rescheduling the off-peak data warehousing jobs. Alternatively, you can disable the off-peak jobs and run them later at a more convenient time.

Note: If you change the job frequency, 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.

Reschedule the Initial Data Warehousing Job

Run the following commands to specify an alternative start time and duration.

SQL Server Host Servers

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 job. For example, set this to 240 to specify a four hour window.

Oracle Host Servers

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.

Disable the Initial Data Warehousing Job

Run the above commands, but set <window> to -1 to disables off-peak jobs. This may be useful, for example, to disable these jobs Monday through Friday but re-enable them over the weekend.

SQL Server Host Servers

Run this command:

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

Oracle Host Servers

Run this command:

BEGIN
  WgnDW_Configure_DW( 
    offpeak_run_starttime_hour => 0, 
    offpeak_run_timeout_mins => -1 );
END;