Loghistory - Definition,Features - Oracle DBA

Discussion

• Nirja Shah   -Posted on 25 Aug 15
  -There are several Scheduler attributes that control the behavior of the Scheduler
  
  They are:
  -default_timezone - Repeating jobs and windows that use the calendaring syntax need to know which time zone to use for their repeat intervals.
  -Scheduler derives the value of default_timezone from the operating system environment.
  -If Scheduler can find no compatible value from the operating system, it sets default_timezone to NULL.
  
  -log_history - This enables you to control the amount of logging the Scheduler performs.
  -To prevent the job log and the window log from growing indiscriminately, the Scheduler has an attribute that specifies how much history (in days) to keep.
  -Once a day, the Scheduler automatically purges all log entries from both the job log as well as the window log that are older than the specified history. The default is 30 days.
  
  -max_job_slave_processes - This enables you to set a maximum number of slave processes for a particular system configuration and load.
  -Even though the Scheduler automatically determines what the optimum number of slave processes is for a given system configuration and load, you still might want to set a fixed limit on the Scheduler.
  -The default value is NULL, and the valid range is 1-999.
  -Although the number set is a real maximum, it does not mean the Scheduler will start the specified number of slaves.
  
  -event_expiry_time - This enables you to set the time in seconds before an event generated by the Scheduler expires (in other words, is automatically purged from the queue).
  

➨ Post your comment / Share knowledge