Pluggable Databases - Expert Consolidation in Oracle Database 12c - page 268

Great! With the resource plan in place, you can enable it as well.
SYSTEM@SWINGBENCH1> alter system set
2 resource_manager_plan = 'swingbench_plan_swingbench1';
System altered.
SYSTEM@SWINGBENCH1> show parameter resource_manager_plan
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
resource_manager_plan string SWINGBENCH_PLAN_SWINGBENCH1
You can view the active resource managers and their settings using the V$RSRC_PLAN dictionary view.
SYS@CDB$ROOT> SELECT PDB.name PDB_NAME,
2 PLN.name PLAN_NAME,
3 PLN.IS_TOP_PLAN,
4 PLN.CON_ID,
5 PLN.PARALLEL_EXECUTION_MANAGED
6 FROM V$RSRC_PLAN PLN,
7 V$PDBS PDB
8 WHERE pln.con_id = pdb.con_id
9 /
PDB_NAME PLAN_NAME IS_TO CON_ID PARALLEL
--------------- -------------------------------- ----- ---------- --------
PDB$SEED INTERNAL_PLAN TRUE 2 FULL
SWINGBENCH1 SWINGBENCH_PLAN_SWINGBENCH1 TRUE 5 FULL
SWINGBENCH2 SWINGBENCH_PLAN_SWINGBENCH2 TRUE 6 FULL
SWINGBENCH3 SWINGBENCH_PLAN_SWINGBENCH3 TRUE 7 FULL
In addition to the dynamic V$-views you will be notified in the alert.log if the plan changes:
Sat Sep 28 20:49:56 2013
Setting Resource Manager plan swingbench_plan_swingbench1 at pdb SWINGBENCH1
(5) via parameter
ALTER SYSTEM SET resource_manager_plan='swingbench_plan_swingbench1' SCOPE=BOTH;
Continuing with the implementation of the user-PDB plan you should be able to cap resource usage for your
PDBs, avoiding conflict with your neighboring databases.
One final step remains: when the user SOE connects to the PDB, then it must be assigned to the appropriate
consumer group. There are a number of ways to achieve this goal, the easiest is to map the user to the resource
consumer group as shown here:
SYSTEM@SWINGBENCH1> begin
2 dbms_resource_manager.create_pending_area;
3 dbms_resource_manager.set_consumer_group_mapping(
4 attribute => DBMS_RESOURCE_MANAGER.ORACLE_USER,
5 value => 'SOE',
6 consumer_group => 'SWINGBENCH_GROUP');