Scheduler Program Options
The following options are available to set in the Oracle Scheduler.
• Business Date: The default value is the database’s current system date, typically useful in cases where jobs run past midnight so same date can be maintained for all job runs. The format is ‘YYYY-MM-DD’. A business date can also be set as SYSDATE or its variance for example SYSDATE-1 or SYSDATE-2.
• User ID: The user ID to use when a batch job is submitted.
• Poll Seconds: The frequency at which batch tables are checked for any updates. Default value is 1 second, but if this adds too much overhead then it can be changed to anywhere between 1 to 60 seconds.
• Notify Job Name: DBMS job OUAF_NOTIFY is the default thread notification job. That is defined out of the box to send emails for every failed thread. If that behavior is undesired, a custom thread notification DBMS job can be created and it defined as the default handler with this option. The new notify DBMS job must exist.
• Thread Notifications: Default value is true and sends thread notifications for failed threads. Can be set to false to suppress the notifications.
• Thread Pool: Default value is DEFAULT, states the thread pool to use for all batch jobs.
• Discard Queue: Set to true to delete all online job queue entries (CI_BATCH_JOB table rows) created by Oracle Scheduler Stored Procedure OUAF_BATCH. The default is false. OUAF_BATCH uses individual CI_BATCH_JOB rows for the threads so it may become quite voluminous, and the job queue entries are typically not useful once a thread has started executing as the batch run tree (BRT) entries are used to track the job. This option can be used to clean up the unused entries.
• Debug: Default value is false. Can be set to true to see internally generated DBMS_OUTPUT debug messages.
• Single Submitter: By default a single batch job submission record is created for all threads of a batch control. Set this to false to create a batch job submission record per thread of a batch control.
Parent topic