The general steps for creating a CDB resource plan for individual PDBs are the following:

The scenario assumes that you want to create a CDB resource plan for a CDB named newcdb. The plan includes a directive for each PDB. In this scenario, you also update the default directive and the AutoTask directive.

The directives are defined using various procedures in the DBMS_RESOURCE_MANAGER package. The attributes of each directive are defined using parameters in these procedures. Table 22-5 describes the types of directives in the plan.

Table 22-6 describes how the CDB resource plan allocates resources to its PDBs using the directive attributes described in Table 22-5.

The salespdb and servicespdb PDBs are more important than the other PDBs in the CDB. Therefore, they get a higher share (3), unlimited CPU utilization resource, and unlimited parallel execution server resource.

The default directive applies to PDBs for which specific directives have not been defined. For this scenario, assume that the CDB has several PDBs that use the default directive. This scenario updates the default directive.

In addition, this scenario updates the AutoTask directive. The AutoTask directive applies to automatic maintenance tasks that are run in the root maintenance window.

To create a CDB resource plan:

1. Create a pending area using the CREATE_PENDING_AREA procedure:

   exec DBMS_RESOURCE_MANAGER.CREATE_PENDING_AREA();

2. Create a CDB resource plan named newcdb_plan using the CREATE_CDB_PLAN procedure:

   BEGIN
     DBMS_RESOURCE_MANAGER.CREATE_CDB_PLAN(
       plan    => 'newcdb_plan',
       comment => 'CDB resource plan for newcdb');
   END;
   /

3. Create the CDB resource plan directives for the PDBs using the CREATE_CDB_PLAN_DIRECTIVE procedure. Each directive specifies how resources are allocated to a specific PDB.

   Table 22-6 describes the directives for the salespdb, servicespdb, and hrpdb PDBs in this scenario. Run the following procedures to create these directives:

   BEGIN
     DBMS_RESOURCE_MANAGER.CREATE_CDB_PLAN_DIRECTIVE(
       plan                  => 'newcdb_plan', 
       pluggable_database    => 'salespdb', 
       shares                => 3, 
       utilization_limit     => 100,
       parallel_server_limit => 100);
   END;
   /
   
   BEGIN
     DBMS_RESOURCE_MANAGER.CREATE_CDB_PLAN_DIRECTIVE(
       plan                  => 'newcdb_plan', 
       pluggable_database    => 'servicespdb', 
       shares                => 3, 
       utilization_limit     => 100,
       parallel_server_limit => 100);
   END;
   /
   
   BEGIN
     DBMS_RESOURCE_MANAGER.CREATE_CDB_PLAN_DIRECTIVE(
       plan                  => 'newcdb_plan', 
       pluggable_database    => 'hrpdb', 
       shares                => 1, 
       utilization_limit     => 70,
       parallel_server_limit => 70);
   END;
   /
   

   All other PDBs in this CDB use the default PDB directive.

4. If the current default CDB resource plan directive for PDBs does not meet your requirements, then update the directive using the UPDATE_CDB_DEFAULT_DIRECTIVE procedure.

   The default directive applies to PDBs for which specific directives have not been defined. See "The Default Directive for PDBs" for more information.

   Table 22-6 describes the default directive that PDBs use in this scenario. Run the following procedure to update the default directive:

   BEGIN
     DBMS_RESOURCE_MANAGER.UPDATE_CDB_DEFAULT_DIRECTIVE(
       plan                      => 'newcdb_plan', 
       new_shares                => 1, 
       new_utilization_limit     => 50,
       new_parallel_server_limit => 50);
   END;
   /

5. Validate the pending area using the VALIDATE_PENDING_AREA procedure:

   exec DBMS_RESOURCE_MANAGER.VALIDATE_PENDING_AREA();

6. Submit the pending area using the SUBMIT_PENDING_AREA procedure:

   exec DBMS_RESOURCE_MANAGER.SUBMIT_PENDING_AREA();

The general steps for creating a CDB resource plan with PDB performance profiles are the following:

The scenario assumes that you want to create a CDB resource plan for a CDB named newcdb. The plan includes a directive for each PDB performance profile. In this scenario, you also update the default directive and the AutoTask directive.

In the CDB resource plan, you give each profile a name. In each PDB, you set the DB_PERFORMANCE_PROFILE initialization parameter to specify which PDB performance profile the PDB uses.

The directives are defined using various procedures in the DBMS_RESOURCE_MANAGER package. The attributes of each directive are defined using parameters in these procedures. The following table describes the types of directives in the plan.

The following table describes how the CDB resource plan allocates resources to its PDB performance profiles using the directive attributes described in Table 22-7.

The default directive applies to PDBs for which specific directives have not been defined. For this scenario, assume that the CDB has several PDBs that use the default directive. This scenario updates the default directive.

In addition, this scenario updates the AutoTask directive. The AutoTask directive applies to automatic maintenance tasks that are run in the root maintenance window.

To create a CDB resource plan for PDB performance profiles:

1. For each PDB that will use a profile, set the DB_PERFORMANCE_PROFILE initialization parameter to the name of the profile that the PDB will use.

   1. Run an ALTER SYSTEM statement to set the parameter.

      For example, with the PDB as the current container, run the following SQL statement:

      ALTER SYSTEM SET DB_PERFORMANCE_PROFILE=gold SCOPE=spfile;

   2. Close the PDB:

      ALTER PLUGGABLE DATABASE CLOSE IMMEDIATE;

   3. Open the PDB:

      ALTER PLUGGABLE DATABASE OPEN;

2. Create a pending area using the CREATE_PENDING_AREA procedure:

   exec DBMS_RESOURCE_MANAGER.CREATE_PENDING_AREA();

3. Create a CDB resource plan named newcdb_plan using the CREATE_CDB_PLAN procedure:

   BEGIN
     DBMS_RESOURCE_MANAGER.CREATE_CDB_PLAN(
       plan    => 'newcdb_plan',
       comment => 'CDB resource plan for newcdb');
   END;
   /

4. Create the CDB resource plan directives for the PDBs using the CREATE_CDB_PLAN_DIRECTIVE procedure. Each directive specifies how resources are allocated to a specific PDB.

   Table 22-6 describes the directives for the gold, silver, and bronze profiles in this scenario. Run the following procedures to create these directives:

   BEGIN
     DBMS_RESOURCE_MANAGER.CREATE_CDB_PROFILE_DIRECTIVE(
       plan                  => 'newcdb_plan', 
       profile               => 'gold', 
       shares                => 3, 
       utilization_limit     => 100,
       parallel_server_limit => 100);
   END;
   /
   
   BEGIN
     DBMS_RESOURCE_MANAGER.CREATE_CDB_PROFILE_DIRECTIVE(
       plan                  => 'newcdb_plan', 
       profile               => 'silver', 
       shares                => 2, 
       utilization_limit     => 40,
       parallel_server_limit => 40);
   END;
   /
   
   BEGIN
     DBMS_RESOURCE_MANAGER.CREATE_CDB_PROFILE_DIRECTIVE(
       plan                  => 'newcdb_plan', 
       profile               => 'bronze', 
       shares                => 1, 
       utilization_limit     => 20,
       parallel_server_limit => 20);
   END;
   /
   

   All other PDBs in this CDB use the default PDB directive.

5. If the current default CDB resource plan directive for PDBs does not meet your requirements, then update the directive using the UPDATE_CDB_DEFAULT_DIRECTIVE procedure.

   The default directive applies to PDBs for which specific directives have not been defined.

   Table 22-6 describes the default directive that PDBs use in this scenario. Run the following procedure to update the default directive:

   BEGIN
     DBMS_RESOURCE_MANAGER.UPDATE_CDB_DEFAULT_DIRECTIVE(
       plan                      => 'newcdb_plan', 
       new_shares                => 1, 
       new_utilization_limit     => 10,
       new_parallel_server_limit => 10);
   END;
   /

6. Validate the pending area using the VALIDATE_PENDING_AREA procedure:

   exec DBMS_RESOURCE_MANAGER.VALIDATE_PENDING_AREA();

7. Submit the pending area using the SUBMIT_PENDING_AREA procedure:

   exec DBMS_RESOURCE_MANAGER.SUBMIT_PENDING_AREA();

This parameter specifies the top plan, which is the plan to be used for the current CDB instance. If no plan is specified with this parameter, then the Resource Manager is not enabled.

Prerequisites

Before enabling a CDB resource plan, complete the prerequisites described in "Overview of Oracle Resource Manager in a Multitenant Environment".

To enable a CDB resource plan:

1. In SQL*Plus, ensure that the current container is the root.

2. Perform one of the following actions:

   • Use an ALTER SYSTEM statement to set the RESOURCE_MANAGER_PLAN initialization parameter to the CDB resource plan.

     The following example sets the CDB resource plan to newcdb_plan using an ALTER SYSTEM statement:

     ALTER SYSTEM SET RESOURCE_MANAGER_PLAN = 'newcdb_plan';
     

   • In a text initialization parameter file, set the RESOURCE_MANAGER_PLAN initialization parameter to the CDB resource plan, and restart the CDB.

     The following example sets the CDB resource plan to newcdb_plan in an initialization parameter file:

     RESOURCE_MANAGER_PLAN = 'newcdb_plan'
     

A CDB resource plan that specifies shares or utilization limits for PDBs is required to enable CPU management, both between PDBs and within a PDB. If a resource plan with shares or utilization limits is enabled for a PDB, and if the CDB resource plan is not specified, then the CDB resource plan is set to DEFAULT_CDB_PLAN. This setting gives equal shares to all PDBs and specifies no utilization limits. To disable CPU resource management throughout the CDB, set RESOURCE_MANAGER_PLAN to ORA$INTERNAL_CDB_PLAN.

Prerequisites

Before disabling a CDB resource plan, complete the prerequisites described in "Overview of Oracle Resource Manager in a Multitenant Environment".

To disable a CDB resource plan:

1. In SQL*Plus, ensure that the current container is the root.

2. Perform one of the following actions:

   • Use an ALTER SYSTEM statement to unset the RESOURCE_MANAGER_PLAN initialization parameter for the CDB.

     The following example unsets the RESOURCE_MANAGER_PLAN initialization parameter using an ALTER SYSTEM statement:

     ALTER SYSTEM SET RESOURCE_MANAGER_PLAN = '';
     

   • In an initialization parameter file, unset the RESOURCE_MANAGER_PLAN initialization parameter, and restart the CDB.

     The following example unsets the RESOURCE_MANAGER_PLAN initialization parameter in an initialization parameter file:

     RESOURCE_MANAGER_PLAN =