New Features for Administrators - Question 042

There is more than one way to set the server to detect and affect long running operations automatically. What is the best choice if you want to reduce the impact of long running operations on other users without aborting the long running operations?

A. Define user profiles and set the CPU_PER_CALL limit.

B. Define a SWITCH_TIME for a plan in the Resource Manager.

C. Create a batch job that checks V$SESSION_LONGOPS; the batch job alters the session priority of the long running operations.

D. Create a user defined event in the Oracle Enterprise Manager, which monitors V$SESSION_LONGOPS.

Answer: B

Explanation:

You can define a SWITCH_TIME for a plan in the Resource Manager to reduce the impact of long running operations on other users without aborting the long running operations.

Incorrect Answers

A: You cannot do this with CPU_PER_CALL limit.

C: You don’t need to use a batch job to check V$SESSION_LONGOPS for this purpose.

D: It can be done with a SWITCH_TIME for a plan in the Resource Manager, you don’t need to monitor V$SESSION_LONGOPS.

OCP Oracle9i Database: New Features for Administrators, Daniel Benjamin, p. 122-129

Chapter 3: Manageability Enhancements