Oracle Oracle Certifications 1Z0-053 Questions & Answers

• Question 601:

  Which of the following is true about job chains?

  A. They consist of one or more Scheduler programs.

  B. They are used to implement dependency scheduling.

  C. They are used to implement time-based scheduling.

  D. They are used to implement event-based scheduling.

  E. None of the above.

  Correct Answer: B

  Creating and Managing Job Chains A job chain ("chain") is a named series of tasks that are linked together for a combined objective. Chains are the means by which you can implement dependency based scheduling, in which jobs are started depending on the outcomes of one or more previous jobs.

• Question 602:

  Which of the following are valid program types for a lightweight job? (Choose all that apply.)

  A. PLSQL_BLOCK

  B. EXECUTABLE

  C. JAVA_STORED_PROCEDURE

  D. STORED_PROCEDURE

  E. EXTERNAL

  Correct Answer: AD

  Job_type

  Job action type ('PLSQL_BLOCK', 'STORED_PROCEDURE', 'EXECUTABLE', or 'CHAIN')

• Question 603:

  When a job exceeds the date specified in its END_DATE attribute, which of the following will happen? (Choose all that apply.)

  A. The job will be dropped automatically if the value of the AUTO_DROP attribute is TRUE.

  B. The job will only be disabled if the value of the AUTO_DROP attribute is FALSE.

  C. The STATE attribute of the job will be set to COMPLETED if the value of the AUTO_DROP attribute is FALSE.

  D. All objects referenced by the job will be dropped if the value of the AUTO_DROP attribute is TRUE and the value of the CASCADE attribute is TRUE.

  E. The STATE column of the job table will be set to COMPLETED for the job.

  Correct Answer: ABC

  auto_drop, If TRUE (the default), indicates that the job should be dropped once completed. end_date, This attribute specifies the date and time after which the job expires and is no longer run. After the end_date, if auto_drop is TRUE, the job is dropped. If auto_drop is FALSE, the job is disabled and the STATE of the job is set to COMPLETED. If no value for end_date is specified, the job repeats forever unless max_runs or max_failures is set, in which case the job stops when either value is reached. The value for end_date must be after the value for start_date. If it is not, an error is generated when the job is enabled.

• Question 604:

  Consider the following code snippet:

  

  If this code were executed, which of the following statements would be true?

  A. The priority of the lne_job1 job would be set to 1.

  B. The lne_job1 job would be executed synchronously.

  C. The lne_job1 job would run immediately in the users current session.

  D. The lne_job1 job would retain its current priority.

  E. The job will immediately take priority over all running jobs.

  Correct Answer: A

  job_priority This attribute specifies the priority of this job relative to other jobs in the same class as this job. If multiple jobs within a class are scheduled to be executed at the same time, the job priority determines the order in which jobs from that class are picked up for execution by the job coordinator. It can be a value from 1 through 5, with 1 being the first to be picked up for job execution.

  If no job priority is specified when creating a job, the default priority of 3 is assigned to it.

• Question 605:

  Which of the following calendaring syntax expressions would evaluate to the last day of every month?

  A. FREQ = MONTHLY; BYMONTHDAY = 31

  B. FREQ = MONTHLY; BYMONTHDAY = -1

  C. FREQ = DAILY; BYDAY = -1

  D. FREQ = MONTHLY; BYDAY = 31

  E. FREQ = DAILY; BYMONTHDAY = LAST_DAY

  Correct Answer: B

  FREQ

  This specifies the type of recurrence. It must be specified. The possible predefined frequency values are YEARLY, MONTHLY, WEEKLY, DAILY, HOURLY, MINUTELY, and SECONDLY. Alternatively, specifies an existing schedule to use as

  a user-defined frequency.

  BYMONTHDAY

  This specifies the day of the month as a number. Valid values are 1 to 31. An example is 10, which means the 10th day of the selected month. You can use the minus sign (-) to count backward from the last day, so, for example,

  BYMONTHDAY=-1 means the last day of the month and BYMONTHDAY=-2 means the next to last day of the month.

• Question 606:

  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

  Correct Answer: AD

  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.

• Question 607:

  Which DBMS_SCHEDULER procedure(s) can be used to alter an existing job? (Choose all that apply.)

  A. SET_ATTRIBUTE_NULL

  B. ALTER_JOB

  C. ALTER_JOB_PARAMETERS

  D. ALTER

  E. SET_ATTRIBUTE

  Correct Answer: AE

  SET_ATTRIBUTE_NULL Procedure, Changes an attribute of an object to NULL SET_ATTRIBUTE Procedure, Changes an attribute of a job, schedule, or other Scheduler object There is NO such "ALTER_JOB", "ALTER_JOB_PARAMETERS" and "ALTER" procedure available.

• Question 608:

  Which Scheduler view(s) can be queried to see which jobs are currently executing? (Choose all that apply.)

  A. DBA_SCHEDULER_JOB_RUN_DETAILS

  B. DBA_SCHEDULER_RUNNING_JOBS

  C. DBA_SCHEDULER_CURRENT_JOBS

  D. DBA_SCHEDULER_JOBS

  E. DBA_SCHEDULER_EXECUTING_JOBS

  Correct Answer: BD

  DBA_SCHEDULER_JOB_RUN_DETAILS displays log run details for all Scheduler jobs in the database. DBA_SCHEDULER_RUNNING_JOBS displays information about all running Scheduler jobs in the database. DBA_SCHEDULER_JOBS displays information about all Scheduler jobs in the database. DBA_SCHEDULER_CURRENT_JOBS is INVALID.

  DBA_SCHEDULER_EXECUTING_JOBS is INVALID.

• Question 609:

  Which of the following is not a valid calendaring syntax element?

  A. FREQ

  B. BYHOUR

  C. RUNDATE

  D. INTERVAL

  E. BYMINUTE

  Correct Answer: C

  Calendaring Syntax (link)

  Table 129-10 Values for repeat_interval

  FREQ

  This specifies the type of recurrence. It must be specified. The possible predefined frequency values are YEARLY, MONTHLY, WEEKLY, DAILY, HOURLY, MINUTELY, and SECONDLY. Alternatively, specifies an existing schedule to use as

  a user-defined frequency.

  INTERVAL

  This specifies a positive integer representing how often the recurrence repeats. The default is 1, which means every second for secondly, every day for daily, and so on. The maximum value is 99.

  BYMONTH

  This specifies which month or months you want the job to execute in. You can use numbers such as 1 for January and 3 for March, as well as three-letter abbreviations such as FEB for February and JUL for July.

  BYWEEKNO

  This specifies the week of the year as a number. It follows ISO-8601, which defines the week as starting with Monday and ending with Sunday; and the first week of a year as the first week, which is mostly within the Gregorian year. The first

  week is equivalent to the following two variants: the week that contains the first Thursday of the Gregorian year; and the week containing January 4th. The ISO-8601 week numbers are integers from 1 to 52 or 53; parts of week 1 may be in

  the previous calendar year; parts of week 52 may be in the following calendar year; and if a year has a week 53, parts of it must be in the following calendar year. As an example, in the year 1998, the ISO week 1 began on Monday December

  29th, 1997;

  and the last ISO week (week 53) ended on Sunday January 3rd, 1999. So December 29th, 1997, is in the ISO week 1998-01, and January 1st, 1999, is in the ISO week 1998-53. byweekno is only valid for YEARLY. Examples of invalid

  specifications are "FREQ=YEARLY; BYWEEKNO=1; BYMONTH=12" and "FREQ=YEARLY; BYWEEKNO=53;BYMONTH=1".

  BYYEARDAY

  This specifies the day of the year as a number. Valid values are 1 to 366. An example is 69, which is March 10 (31 for January, 28 for February, and 10 for March). 69 evaluates to March 10 for non-leap years and March 9 in leap years. -2 will

  always evaluate to December 30th independent of whether it is a leap year.

  BYDATE

  This specifies a list of dates, where each date is of the form [YYYY] MMDD. A list of consecutive dates can be generated by using the SPAN modifier, and a date can be adjusted with the OFFSET modifier. An example of a simple BYDATE

  clause follows:

  BYDATE=0115,0315,0615,0915,1215,20060115 The following SPAN example is equivalent to

  BYDATE=0110,0111,0112,0113,0114, which is a span of 5 days starting at 1/10:

  BYDATE=0110+SPAN:5D

  The plus sign in front of the SPAN keyword indicates a span starting at the supplied date. The minus sign indicates a span ending at the supplied date, and the "^" sign indicates a span of n days or weeks centered around the supplied date. If

  n is an even number, it is adjusted up to the next odd number.

  Offsets adjust the supplied date by adding or subtracting n days or weeks. BYDATE=0205- OFFSET: 2W is equivalent to BYDATE=0205-14D (the OFFSET: keyword is optional), which is also equivalent to BYDATE=0122.

  BYMONTHDAY

  This specifies the day of the month as a number. Valid values are 1 to 31. An example is 10, which means the 10th day of the selected month. You can use the minus sign (-) to count backward from the last day, so, for example,

  BYMONTHDAY=-1 means the last day of the month and BYMONTHDAY=-2 means the next to last day of the month.

  BYDAY

  This specifies the day of the week from Monday to Sunday in the form MON, TUE, and so on. Using numbers, you can specify the 26th Friday of the year, if using a YEARLY frequency, or the 4th THU of the month, using a MONTHLY

  frequency. Using the minus sign, you can say the second to last Friday of the month. For example, -1 FRI is the last Friday of the month.

  BYHOUR

  This specifies the hour on which the job is to run. Valid values are 0 to 23. As an example, 10 means 10 m.

  BYMINUTE

  This specifies the minute on which the job is to run. Valid values are 0 to 59. As an example, 45 means 45 minutes past the chosen hour.

  BYSECOND

  This specifies the second on which the job is to run. Valid values are 0 to 59. As an example, 30 means 30 seconds past the chosen minute.

  BYSETPOS

  This selects one or more items, by position, in the list of timestamps that result after the whole calendaring expression is evaluated. It is useful for requirements such as running a job on the last workday of the month. Rather than attempting to

  express this with the other BY clauses, you can code the calendaring expression to evaluate to a list of every workday of the month, and then add the BYSETPOS clause to select only the last item of that list. Assuming that workdays are

  Monday through Friday, the syntax would then be:

  FREQ=MONTHLY; BYDAY=MON,TUE,WED,THU,FRI; BYSETPOS=-1

  Valid values are 1 through 9999. A negative number selects an item from the end of the list (-1 is the last item, -2 is the next to last item, and so on) and a positive number selects from the front of the list. The BYSETPOS clause is always

  evaluated last. BYSETPOS is only supported with the MONTHLY and YEARLY frequencies. The BYSETPOS clause is applied to the list of timestamps once per frequency period. For example, when the frequency is defined as MONTHLY,

  the Scheduler determines all valid timestamps for the month, orders that list, and then applies the BYSETPOS clause. The Scheduler then moves on to the next month and repeats the procedure. Assuming a start date of Jun 10, 2004, the

  example evaluates to: Jun 30, Jul 30, Aug 31, Sep 30, Oct 29, and so on.

  INCLUDE

  This includes one or more named schedules in the calendaring expression. That is, the set of timestamps defined by each included named schedule is added to the results of the calendaring expression. If an identical timestamp is contributed

  by both an included schedule and the calendaring expression, it is included in the resulting set of timestamps only once. The named schedules must have been defined with the CREATE_SCHEDULE procedure.

  EXCLUDE

  This excludes one or more named schedules from the calendaring expression. That is, the set of timestamps defined by each excluded named schedule is removed from the results of the calendaring expression. The named schedules must

  have been defined with the CREATE_SCHEDULE procedure.

  INTERSECT

  This specifies an intersection between the calendaring expression results and the set of timestamps defined by one or more named schedules. Only the timestamps that appear both in the calendaring expression and in one of the named

  schedules are included in the resulting set of timestamps. For example, assume that the named schedule last_sat indicates the last Saturday in every month, and that for the year 2005, the only months where the last day of the month is also

  a Saturday are April and December.

  Assume also that the named schedule end_qtr indicates the last day of each quarter in 2005:

  3/31/2005, 6/30/2005, 9/30/2005, 12/31/2005 These calendaring expressions result in the dates that follow:

  3/31/2005, 4/30/2005, 6/30/2005, 9/30/2005, 12/31/2005 FREQ=MONTHLY; BYMONTHDAY=-1;

  INTERSECT=last_sat,end_qtr In this example, the terms FREQ=MONTHLY; BYMONTHDAY=-1 indicate the last day of each month.

  PERIODS

  This identifies the number of periods that together form one cycle of a user-defined frequency. It is used in the repeat_interval expression of the schedule that defines the user-defined frequency. It is mandatory when the repeat_interval expression in the main schedule contains a BYPERIOD clause. The following example defines the quarters of a fiscal year.

  FREQ=YEARLY;BYDATE=0301,0601,0901,1201;PERIODS=4

  BYPERIOD This selects periods from a user-defined frequency. For example, if a main schedule names a user-defined frequency schedule that defines the fiscal quarters shown in the previous example, the clause BYPERIOD=2,4 in the main schedule selects the 2nd and 4th fiscal quarters.

• Question 610:

  You create two resource plans, one for data warehouse loading jobs at night and the other for application jobs at day time. You want the resource plans to activate automatically so that the resource allocation is optimum as desired by the activity.

  How would you achieve this?

  A. Implement job classes

  B. Implement Scheduler windows

  C. Implement the mapping rule for the consumer groups

  D. Set the SWITCH_TIME resource plan directive for both the resource plans

  Correct Answer: B