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

 

99.View the Exhibit and examine the steps that you executed to create a database resource plan.

Subsequently, you execute the following procedure which results in an error:

SQL> EXECUTE dbms_resources_manager.validate_pending_area ( );

What could be the reason?

Exhibit:

A. The pending area is automatically submitted after the plan creation

B. The procedure must be executed before creating the resources plan directive

C. The SYS_GROUP resource consumer group is not included in the resource plan directive

D. The OTHER_GROUPS resources consumer group is not included in the resource plan directive

Answer: D

答案解析：

参考：http://docs.oracle.com/cd/E11882_01/server.112/e25494/dbrm.htm#ADMIN11871

Validating the Pending Area

At any time when you are making changes in the pending area, you can call VALIDATE_PENDING_AREA to ensure that the pending area is valid so far.

The following rules must be adhered to, and are checked by the validate procedure:

• No plan can contain any loops. A loop occurs when a subplan contains a directive that references a plan that is above the subplan in the plan hierarchy. For example, a subplan cannot reference the top plan.

• All plans and resource consumer groups referred to by plan directives must exist.

• All plans must have plan directives that point to either plans or resource consumer groups.

• All percentages in any given level must not add up to greater than 100.

• A plan that is currently being used as a top plan by an active instance cannot be deleted.

• The following parameters can appear only in plan directives that refer to resource consumer groups, not other resource plans:

  • PARALLEL_DEGREE_LIMIT_P1

  • ACTIVE_SESS_POOL_P1

  • QUEUEING_P1

  • SWITCH_GROUP

  • SWITCH_TIME

  • SWITCH_ESTIMATE

  • SWITCH_IO_REQS

  • SWITCH_IO_MEGABYTES

  • MAX_EST_EXEC_TIME

  • UNDO_POOL

  • MAX_IDLE_TIME

  • MAX_IDLE_BLOCKER_TIME

  • SWITCH_FOR_CALL

  • MAX_UTILIZATION_LIMIT

• There can be no more than 28 resource consumer groups in any active plan. Also, at most, a plan can have 28 children.

• Plans and resource consumer groups cannot have the same name.

• There must be a plan directive for OTHER_GROUPS somewhere in any active plan. This ensures that a session that is not part of any of the consumer groups included in the currently active plan is allocated resources (as specified by the directive for OTHER_GROUPS).

VALIDATE_PENDING_AREA raises an error if any of the preceding rules are violated. You can then make changes to fix any problems and call the procedure again.

It is possible to create "orphan" consumer groups that have no plan directives referring to them. This allows the creation of consumer groups that will not currently be used, but might be part of some plan to be implemented in the future.

Example: Validating the Pending Area:

The following PL/SQL block validates the pending area.

BEGIN

  DBMS_RESOURCE_MANAGER.VALIDATE_PENDING_AREA();

END;

/