OCP-1Z0-053-V13.02-651题

651.The user SYS creates a job by using the following command:



Which two statements are true about the job that was created by the preceding command? (Choose two.)

A. The job is enabled by default after creation

B. The job is automatically dropped after the end date

C. The job executes with the privileges of the user SYS

D. The globalization environment that exists at the time of the job creation prevails at the job runs

Answer: BC

答案解析：

By default, jobs are created with

auto_drop

set to

TRUE

. f

auto_drop

is

TRUE

,
the job is dropped.--B正确。

Jobs are created as disabled by default. --A错误

repeat_interval

This attribute specifies how often the job repeats. You can specify the repeat interval by using calendaring or PL/SQL expressions. The expression specified is evaluated to determine the next time the job should run. If repeat_interval is not specified, the job runs only once at the specified start date.

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.

auto_drop

This flag, if TRUE , causes a job to be automatically dropped after it has completed or has been automatically disabled. A job is considered completed if: Its end date (or the end date of the job schedule) has passed. It has run max_runs number of times. max_runs must be set with SET_ATTRIBUTE . It is not a repeating job and has run once. A job is disabled when it has failed max_failures times. max_failures is also set with SET_ATTRIBUTE . If this flag is set to FALSE , the jobs are not dropped and their metadata is kept until the job is explicitly dropped with the DROP_JOB procedure. By default, jobs are created with auto_drop set to TRUE .

Usage Notes
Jobs are created as disabled by default. You must explicitly enable them so that they will become active and scheduled. Before enabling a job, ensure that all program arguments, if any, are defined,
either by defining default values in the program object or by supplying values with the job.

The

JOB_QUEUE_PROCESSES

initialization parameter specifies the maximum number of processes that can be created for the execution of jobs. Beginning with Oracle Database 11g Release 2 (11.2),

JOB_QUEUE_PROCESSES

applies
to

DBMS_SCHEDULER

jobs. Setting this parameter to 0 disables

DBMS_SCHEDULER

jobs.
To create a job in your own schema, you need to have the

CREATE

JOB

privilege. A user with the

CREATE

ANY

JOB

privilege
can create a job in any schema. If the job being created will reside in another schema, the job name must be qualified with the schema name. For a job of type

EXECUTABLE

(or for a job that points to a program
of type

EXECUTABLE

), the job owner must have the

CREATE EXTERNAL JOB

system privilege before the job can be enabled or run.

Associating a job with a particular class or program requires

EXECUTE

privileges for that class or program.
Not all possible job attributes can be set with

CREATE_JOB

. Some must be set after the job is created. For example, job arguments must be set with theSET_JOB_ARGUMENT_VALUE
Procedure or the SET_JOB_ANYDATA_VALUE Procedure. Other job attributes, such as

job_priority

and

max_runs

,
are set with the SET_ATTRIBUTE Procedure.
To create multiple jobs efficiently, use the

CREATE_JOBS

procedure.