Which three statements are true about persistent lightweight jobs?

Which three statements are true about persistent lightweight jobs?

Which three statements are true about persistent lightweight jobs?

A.
A user cannot set privileges on them.

B.
They generate large amounts of metadata.

C.
They may be created as fully self-contained jobs.

D.
They must reference an existing Scheduler Program.

E.
The are useful when users need to create a large number of jobs quickly.



Leave a Reply 8

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


vijay

vijay

A , D and E

Siegfried

Siegfried

A,D,E
http://docs.oracle.com/database/121/ADMIN/schedover.htm#ADMIN12668
Unlike regular jobs, they are not schema objects.
Because lightweight jobs are not schema objects, you cannot grant privileges on them. A lightweight job inherits privileges from its specified program. Thus, any user who has a certain set of privileges on the program has corresponding privileges on the lightweight job.
Use lightweight jobs when you have many short-duration jobs that run frequently. Under certain circumstances, using lightweight jobs can deliver a small performance gain.
A lightweight job must reference a program object (program) to specify a job action. The program must be already enabled when the lightweight job is created, and the program type must be either ‘PLSQL_BLOCK’ or ‘STORED_PROCEDURE’.

Tri

Tri

A, D , E

Tri

Tri

Again A,D,E. Thanks Seigfried

http://docs.oracle.com/database/121/ADMIN/schedover.htm#ADMIN12668
Unlike regular jobs, they are not schema objects.
Because lightweight jobs are not schema objects, you cannot grant privileges on them. A lightweight job inherits privileges from its specified program. Thus, any user who has a certain set of privileges on the program has corresponding privileges on the lightweight job.
Use lightweight jobs when you have many short-duration jobs that run frequently. Under certain circumstances, using lightweight jobs can deliver a small performance gain.
A lightweight job must reference a program object (program) to specify a job action. The program must be already enabled when the lightweight job is created, and the program type must be either ‘PLSQL_BLOCK’ or ‘STORED_PROCEDURE’.

readyplayerone

readyplayerone

From http://docs.oracle.com/cd/B28359_01/server.111/b28310/schedover004.htm#BGBJGHBH:

They have a significant improvement in create and drop time over regular jobs because they do not have the overhead of creating a schema object.****(>>>E<<>>D<<>>A<<<)****. A lightweight job inherits privileges from its specified program. Thus, any user who has a certain set of privileges on the program has corresponding privileges on the lightweight job.

So, ADE.