What is the danger associated with stopping a running job by using the STOP_JOB procedure?

What is the danger associated with stopping a running job by using the STOP_JOB
procedure?

What is the danger associated with stopping a running job by using the STOP_JOB
procedure?

A.
The job will need to be reenabled before it will execute again.

B.
The job may hold locks on objects referenced within it.

C.
All jobs within the job group will also be stopped.

D.
The job may leave data in an inconsistent state.

E.
There is no danger in using the STOP_JOB procedure.



Leave a Reply 1

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


Eamon

Eamon

According to teh book that prnted this question the answer is …
16. D. The Scheduler will attempt to wrap the job within a transaction and will execute a rollback if a job is stopped. However, if the job has performed COMMITs, the rollback will roll back only uncommitted changes. This could result in inconsistent data.

Also Wont be on the exam