Configuring Background Periodic Reports

This section describes the configuration of Background Periodic Reports.

You must ensure that you adhere to the following points while configuring Background Periodic Reports:

1. No new AG task is required. You can simply use the existing Batch Periodic Reports. You need to create one iteration of the task for every periodic report you want to run in parallel. For example, if you'd like Oracle Argus Safety to generate only 1 periodic report at a time then configure 1 Oracle Argus Safety Service process for Batch Periodic Reports, but if you'd like Oracle Argus Safety to generate up to 5 periodic reports in parallel then configure 5 Oracle Argus Safety Service processes for Batch Periodic Reports, each one using a unique Oracle Argus Safety Service named account.
2. You must also consider the average duration of a report and the number of reports when deciding on the number of Batch Periodic Reports processes that need to be configured. If one process does not suffice, multiple processes can be created on the same server. However, if multiple processes cause consistently high CPU and memory utilization, a new server may be required to support the additional processes.
3. The Interval setting for the Batch Periodic Reports process should be based on the average time taken to generate a report and the number of reports generated on a day. Ideally, all reports for a day should be generated on the same day itself.