which parameters of the SET_SCHEDULER_ATTRIBUTE procedure need to be used?

To set the history retention period for either window logging or job logging individually, which
parameters of the SET_SCHEDULER_ATTRIBUTE procedure need to be used? (Choose all
that apply.)

To set the history retention period for either window logging or job logging individually, which
parameters of the SET_SCHEDULER_ATTRIBUTE procedure need to be used? (Choose all
that apply.)

A.
LOG_HISTORY

B.
JOB_LOG_RETENTION

C.
WINDOW_LOG_RETENTION

D.
WHICH_LOG

E.
LOG_NAME

Explanation:
———————————————-
Attributes list of SET_SCHEDULE_ATTRIBUTE:
‘default_timezone’: Repeating jobs and windows that use the calendaring syntax retrieve the
time
zone from this attribute when start_date is not specified. See “Calendaring Syntax” for more
information.
’email_server’: The SMTP server address that the Scheduler uses to send e-mail
notifications for job state events. E-mail notifications cannot be sent if this attribute is NULL.
’email_sender’: The default e-mail address of the sender of job state e-mail notifications.
’email_server_credential’: The schema and name of an existing credential object that SYS
has execute object privileges on. Default is NULL. The username and password stored in
this credential are used to authenticate with the e-mail server when sending e-mail
notifications. This functionality is available with Oracle Database 11g Release 2 (11.2.0.2).
’email_server_encryption’: This attribute indicates whether or not encryption is enabled for
this email server connection, and if so, at what point encryption starts, and with which
protocol. This functionality is available starting with Oracle Database 11g Release 2
(11.2.0.2). Values are:
NONE: the default, indicating no encryption used
SSL_TLS: indicating that either SSL or TLS are used, from the beginning of the connection
STARTTLS:indicating that the connection starts unencrypted, but the command STARTTLS
is sent to the e-mail server and starts encryption
‘event_expiry_time’: The time, in seconds, before a job state event generated by the
Scheduler expires from the Scheduler event queue. If NULL, job state events expire after 24
hours.
‘log_history’: The number of days that log entries for both the job log and the window log are
retained. Default is 30 and the range of valid values is 0 through 1000000.
‘max_job_slave_processes’: This Scheduler attribute is not used.
The PURGE_LOG Procedure uses “WHICH_LOG” and “LOG_NAME” attributes.
Syntax

Parameters
log_history

This specifies how much history (in days) to keep. The valid range is 0 – 1000000. If set to 0,
no history is kept.
which_log
This specifies the log type. Valid values are: job_log, window_log, and job_and_window_log.
job_name
This specifies which job-specific entries must be purged from the jog log. This can be a
comma-delimited list of job names and job classes. Whenever job_name has a value other
than NULL, the which_log argument implicitly includes the job log.



Leave a Reply 0

Your email address will not be published. Required fields are marked *