157 DBMS_RESOURCE_MANAGER
The DBMS_RESOURCE_MANAGER
package maintains plans, consumer groups, and plan directives. It also provides semantics so that you may group together changes to the plan schema.
This chapter contains the following topics:
See Also:
For more information on using the Database Resource Manager, see Oracle Database Administrator’s Guide
157.1 DBMS_RESOURCE_MANAGER Deprecated Subprograms
The SET_INITIAL_CONSUMER_GROUP Procedure has been deprecated with Oracle Database 11g.
Note:
Oracle recommends that you do not use deprecated procedures in new applications. Support for deprecated features is for backward compatibility only.
157.2 DBMS_RESOURCE_MANAGER Security Model
The invoker must have the ADMINISTER_RESOURCE_MANAGER
system privilege to execute these procedures.
The procedures to grant and revoke this privilege are in the package DBMS_RESOURCE_MANAGER_PRIVS.
157.3 DBMS_RESOURCE_MANAGER Constants
The DBMS_RESOURCE_MANAGER
package defines several constants for specifying parameter values.
These are shown in the following table.
Table 157-1 DBMS_RESOURCE_MANAGER Constants
Constant | Type | Value | Description |
---|---|---|---|
|
|
|
Client identifier of the session |
|
|
|
Name of the computer from which the client is making the connection |
|
|
|
Operating system user name of the client that is logging in |
|
|
|
Name of the client program used to log in to the server |
|
|
|
Module name in the currently running application as set by the SET_MODULE Procedure in the DBMS_APPLICATION_INFO package, or the equivalent OCI attribute setting |
|
|
|
A combination of the current module and the action being performed as set by either of the following procedures in the DBMS_APPLICATION_INFO package, or their equivalent OCI attribute setting: The attribute is specified as the module name followed by a period (.), followed by the action name (module_name.action_name). |
|
|
|
Function the session is currently executing. Valid functions are the |
|
|
|
Oracle Database user name |
|
|
|
Combination of service and module names in this form: service_name.module_name |
|
|
|
Combination of service name, module name, and action name, in this form: service_name.module_name.action_name |
|
|
|
Service name used by the client to establish a connection |
157.4 Summary of DBMS_RESOURCE_MANAGER Subprograms
This table lists the DBMS_RESOURCE_MANAGER
subprograms and briefly describes them.
Table 157-2 DBMS_RESOURCE_MANAGER Package Subprograms
Subprogram | Description |
---|---|
Indicates the start of a block of SQL statements to be treated as a group by resource manager |
|
Calibrates the I/O capabilities of storage |
|
Clears the work area for the resource manager |
|
Creates a new resource consumer group category |
|
Creates entries which define consolidation resource plans. |
|
Creates the plan directives of the consolidation resource plan |
|
Creates the performance profile directives of the consolidation resource plan |
|
Creates entries which define resource consumer groups |
|
Creates a work area for changes to resource manager objects |
|
Creates entries which define resource plans |
|
Creates resource plan directives |
|
Creates a single-level resource plan containing up to eight consumer groups in one step |
|
Deletes an existing resource consumer group category |
|
Deletes the consolidation resource plan |
|
Deletes the plan directive of the consolidation resource plan |
|
Deletes the performance profile directive of the consolidation resource plan |
|
Deletes entries which define resource consumer groups |
|
Deletes the specified plan as well as all the plan directives it refers to |
|
Deletes the specified plan as well as all its descendants (plan directives, subplans, consumer groups) |
|
Deletes resource plan directives |
|
Dequeues a parallel statement from the parallel statement queue |
|
Indicates the end of a block of SQL statements that should be treated as a group by resource manager |
|
Adds, deletes, or modifies entries for the login and run-time attribute mappings |
|
Creates the session attribute mapping priority list |
|
Assigns the initial resource consumer group for a user (Caution: Deprecated Subprogram) |
|
Submits pending changes for the resource manager |
|
Changes the resource consumer group of a specific session |
|
Changes the resource consumer group for all sessions with a given user name |
|
Sets the current resource manager plan |
|
Updates an existing resource consumer group category |
|
Updates the plan directives with regard to automated maintenance tasks |
|
Updates the default values for a consolidation plan |
|
Updates the consolidation resource plan |
|
Updates the plan directives for a consolidation resource plan |
|
Updates the performance profile directives of the consolidation resource plan |
|
Updates entries which define resource consumer groups |
|
Updates entries which define resource plans |
|
Updates resource plan directives |
|
Validates pending changes for the resource manager |
157.4.1 BEGIN_SQL_BLOCK Procedure
This procedure, to be used with parallel statement queuing, indicates the start of a block of SQL statements that should be treated as a group by resource manager.
Syntax
DBMS_RESOURCE_MANAGER.BEGIN_SQL_BLOCK;
Usage Notes
For more information, see "Parallel Statement Queuing" and "Managing Parallel Statement Queuing with Resource Manager" in Oracle Database VLDB and Partitioning Guide.
157.4.2 CALIBRATE_IO Procedure
This procedure calibrates the I/O capabilities of storage. Calibration status is available from the V$IO_CALIBRATION_STATUS
view and results for a successful calibration run are located in DBA_RSRC_IO_CALIBRATE
table.
Syntax
DBMS_RESOURCE_MANAGER.CALIBRATE_IO ( num_physical_disks IN PLS_INTEGER DEFAULT 1, max_latency IN PLS_INTEGER DEFAULT 20, max_iops OUT PLS_INTEGER, max_mbps OUT PLS_INTEGER, actual_latency OUT PLS_INTEGER);
Parameters
Table 157-3 CALIBRATE_IO Procedure Parameters
Parameter | Description |
---|---|
|
Approximate number of physical disks in the database storage. This parameter is used to determine the initial I/O load for the calibration run. |
|
Maximum tolerable latency in milliseconds for database-block-sized IO requests |
|
Maximum number of I/O requests per second that can be sustained. The I/O requests are randomly-distributed, database-block-sized reads. |
|
Maximum throughput of I/O that can be sustained, expressed in megabytes per second. The I/O requests are randomly-distributed, 1 megabyte reads. |
|
Average latency of database-block-sized I/O requests at |
Usage Notes
-
Only users with the SYSDBA privilege can run this procedure. Qualified users must also turn on
timed_statistics
, and ensureasynch_io
is enabled for datafiles. This can be achieved by settingfilesystemio_options
to eitherASYNCH
orSETALL
. One can also query theasynch_io
status by means of the following SQL statement:col name format a50 SELECT name, asynch_io FROM v$datafile f,v$iostat_file i WHERE f.file# = i.file_no AND filetype_name = 'Data File' /
-
Only one calibration can be run at a time. If another calibration is initiated at the same time, it will fail.
-
For an Oracle Real Application Clusters (Oracle RAC) database, the workload is simultaneously generated from all instances.
-
In a multitenant container database (CDB), calibration can only be run from the CDB root (
CDB$ROOT
). -
Calibration is extremely disruptive to the database performance. It is strongly recommended to run calibration only when database users can tolerate severe deterioration to database performance.
-
For optimal calibration results, no other database workloads should be running.
See Also:
Oracle Database Performance Tuning Guide for more information about calibration
Examples
Example of using I/O Calibration procedure
SET SERVEROUTPUT ON DECLARE lat NUMBER; iops INTEGER; mbps INTEGER; BEGIN -- DBMS_RESOURCE_MANAGER.CALIBRATE_IO (<DISKS>, <MAX_LATENCY>, iops, mbps, lat); DBMS_RESOURCE_MANAGER.CALIBRATE_IO (2, 10, iops, mbps, lat); end; /
View for I/O calibration results
SQL> desc V$IO_CALIBRATION_STATUS Name Null? Type ----------------------------------------- -------- ---------------------------- STATUS VARCHAR2(13) CALIBRATION_TIME TIMESTAMP(3) SQL> desc gv$io_calibration_status Name Null? Type ----------------------------------------- -------- ---------------------------- INST_ID NUMBER STATUS VARCHAR2(13) CALIBRATION_TIME TIMESTAMP(3) Column explanation: ------------------- STATUS: IN PROGRESS : Calibration in Progress (Results from previous calibration run displayed, if available) READY : Results ready and available from earlier run NOT AVAILABLE : Calibration results not available. CALIBRATION_TIME: End time of the last calibration run
DBA table that stores I/O Calibration results
SQL> desc DBA_RSRC_IO_CALIBRATE Name Null? Type ----------------------------------------- -------- ---------------------------- START_TIME TIMESTAMP(6) END_TIME TIMESTAMP(6) MAX_IOPS NUMBER MAX_MBPS NUMBER MAX_PMBPS NUMBER LATENCY NUMBER NUM_PHYSICAL_DISKS NUMBER comment on table DBA_RSRC_IO_CALIBRATE is 'Results of the most recent I/O calibration' / comment on column DBA_RSRC_IO_CALIBRATE.START_TIME is 'start time of the most recent I/O calibration' / comment on column DBA_RSRC_IO_CALIBRATE.END_TIME is 'end time of the most recent I/O calibration' / comment on column DBA_RSRC_IO_CALIBRATE.MAX_IOPS is 'maximum number of data-block read requests that can be sustained per second' / comment on column DBA_RSRC_IO_CALIBRATE.MAX_MBPS is 'maximum megabytes per second of maximum-sized read requests that can be sustained' / comment on column DBA_RSRC_IO_CALIBRATE.MAX_PMBPS is 'maximum megabytes per second of large I/O requests that can be sustained by a single process' / comment on column DBA_RSRC_IO_CALIBRATE.LATENCY is 'latency for data-block read requests' / comment on column DBA_RSRC_IO_CALIBRATE.NUM_PHYSICAL_DISKS is 'number of physical disks in the storage subsystem (as specified by user)' /
157.4.3 CLEAR_PENDING_AREA Procedure
This procedure clears pending changes for the resource manager.
Syntax
DBMS_RESOURCE_MANAGER.CLEAR_PENDING_AREA;
157.4.4 CREATE_CATEGORY Procedure
This procedure creates a new consumer group category. The primary purpose of this attribute is to support Exadata I/O Resource Manager category plans.
The view DBA_RSRC_CATEGORIES
defines the currently defined categories. The ADMINISTRATIVE
, INTERACTIVE
, BATCH
, MAINTENANCE
, and OTHER
categories are available.
Syntax
DBMS_RESOURCE_MANAGER.CREATE_CATEGORY ( category IN VARCHAR2, comment IN VARCHAR2 DEFAULT NULL);
Parameters
Table 157-4 CREATE_CATEGORY Procedure Parameters
Parameter | Description |
---|---|
|
Name of consumer group category |
|
User comment |
157.4.5 CREATE_CDB_PLAN Procedure
Creates entries which define consolidation resource plans.
Syntax
DBMS_RESOURCE_MANAGER.CREATE_CDB_PLAN ( plan IN VARCHAR2(32), comment IN VARCHAR2(2000) DEFAULT NULL);
Parameters
Table 157-5 CREATE_CDB_PLAN Procedure Parameters
Parameter | Description |
---|---|
|
Name of the consolidation plan |
|
User comment |
Usage Notes
This procedure can be run only from the CDB root (CDB$ROOT
).
157.4.6 CREATE_CDB_PLAN_DIRECTIVE Procedure
This procedure creates the plan directives of the consolidation resource plan. Plan directives specify the resource allocation policy for pluggable databases (PDBs).
Syntax
DBMS_RESOURCE_MANAGER.CREATE_CDB_PLAN_DIRECTIVE ( plan IN VARCHAR2, pluggable_database IN VARCHAR2, comment IN VARCHAR2 (2000) DEFAULT '', shares IN NUMBER DEFAULT NULL, utilization_limit IN NUMBER DEFAULT NULL, parallel_server_limit IN NUMBER DEFAULT NULL, memory_limit IN NUMBER DEFAULT 100, memory_min IN NUMBER DEFAULT 0);
Parameters
Table 157-6 CREATE_CDB_PLAN_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the consolidation plan |
|
Name of the PDB |
|
User comment |
|
Specifies the share of resource allocation for the PDB. CPU Resource Manager and Exadata I/O Resource Manager are enabled by specifying shares for each PDB. The |
|
Specifies the maximum percentage of the CDB's CPU and Exadata I/O resources that the PDB can utilize. CPU Resource Manager and Exadata I/O Resource Manager can also be limited by setting the |
|
Parallel servers that the PDB can use after which parallel statements are queued. Alternatively, you can set the A PDB can set a lower limit for parallel execution servers than the limit specified in the CDB resource plan. When the For example, assume that the Note: Oracle recommends, that you use |
|
This parameter is only applicable to Oracle Exadata storage for configuring the Exadata Smart Flash Cache and Exadata PMEM Cache. |
|
This parameter is only applicable to Oracle Exadata storage for configuring the Exadata Smart Flash Cache and Exadata PMEM Cache. |
Usage Notes
-
The default value for
shares
,utilization_limit
, andparallel_server_limit
isNULL
. When a user specifiesNULL
, or does not specify a value, this indicates that the default value should be used. -
This procedure can be run only from the CDB root (
CDB$ROOT
).
157.4.7 CREATE_CDB_PROFILE_DIRECTIVE Procedure
This procedure creates the performance profile directives of the consolidation resource plan. The directives specify the resource allocation policy for pluggable databases (PDBs) that use the performance profile.
For a PDB to use the new performance profile, the PDB must have the DB_PERFORMANCE_PROFILE
initialization parameter set to the profile name.
This procedure provides an easy way to specify the directive for a large number of PDBs with the same resource requirements. Each PDB with a DB_PERFORMANCE_PROFILE
initialization parameter set to the performance profile name inherits the settings specified by this directive, including the shares, utilization limit, and so on.
Syntax
DBMS_RESOURCE_MANAGER.CREATE_CDB_PROFILE_DIRECTIVE ( plan IN VARCHAR2, profile IN VARCHAR2, comment IN VARCHAR2 (2000) DEFAULT '', shares IN NUMBER DEFAULT NULL, utilization_limit IN NUMBER DEFAULT NULL, parallel_server_limit IN NUMBER DEFAULT NULL, memory_limit IN NUMBER DEFAULT 100, memory_min IN NUMBER DEFAULT 0);
Parameters
Table 157-7 CREATE_CDB_PROFILE_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the consolidation plan |
|
Name of the performance profile |
|
User comment |
|
Specifies the share of resource allocation for PDBs that use the performance profile. CPU Resource Manager and Exadata I/O Resource Manager are enabled by specifying shares for each PDB. The |
|
Specifies the maximum percentage of CPU Resource Manager and Exadata I/O Resource Manager that PDBs that use the performance profile can utilize. |
|
Specifies the maximum percentage of |
|
This parameter is only applicable to Oracle Exadata storage for configuring the Exadata Smart Flash Cache and Exadata PMEM Cache. |
|
This parameter is only applicable to Oracle Exadata storage for configuring the Exadata Smart Flash Cache and Exadata PMEM Cache. |
157.4.8 CREATE_CONSUMER_GROUP Procedure
This procedure creates entries which define resource consumer groups.
Syntax
DBMS_RESOURCE_MANAGER.CREATE_CONSUMER_GROUP ( consumer_group IN VARCHAR2, comment IN VARCHAR2 DEFAULT NULL, cpu_mth IN VARCHAR2 DEFAULT NULL, mgmt_mth IN VARCHAR2 DEFAULT 'ROUND-ROBIN', category IN VARCHAR2 DEFAULT 'OTHER');
Parameters
Table 157-8 CREATE_CONSUMER_GROUP Procedure Parameters
Parameter | Description |
---|---|
|
Name of the consumer group |
|
User comment |
|
Name of CPU resource allocation method (deprecated) |
|
Name of CPU resource allocation method |
|
Describes the category of the consumer group. The primary purpose of this attribute is to support Exadata I/O Resource Manager category plans. The view |
157.4.9 CREATE_PENDING_AREA Procedure
This procedure makes changes to resource manager objects.
All changes to the plan schema must be done within a pending area. The pending area can be thought of as a "scratch" area for plan schema changes. The administrator creates this pending area, makes changes as necessary, possibly validates these changes, and only when the submit is completed do these changes become active.
Syntax
DBMS_RESOURCE_MANAGER.CREATE_PENDING_AREA;
Usage Notes
You may, at any time while the pending area is active, view the current plan schema with your changes by selecting from the appropriate user views.
At any time, you may clear the pending area if you want to stop the current changes. You may also call the VALIDATE
procedure to confirm whether the changes you have made are valid. You do not have to perform your changes in a given order to maintain a consistent group of entries. These checks are also implicitly done when the pending area is submitted.
Note:
Oracle allows "orphan" consumer groups (in other words, consumer groups that have no plan directives that refer to them). This is in anticipation that an administrator may want to create a consumer group that is not currently being used, but will be used in the future.
For resource plans, the following rules must be adhered to, and they are checked whenever the validate or submit procedures are executed:
-
No plan schema may contain any loops.
-
All plans and consumer groups referred to by plan directives must exist.
-
All plans must have plan directives that refer to either plans or consumer groups.
-
All percentages in any given level must not add up to greater than 100 for the emphasis resource allocation method.
-
No plan may be deleted that is currently being used as a top plan by an active instance.
-
The plan directive parameter,
parallel_degree_limit_p1
, may only appear in plan directives that refer to consumer groups (that is, not at subplans). -
There cannot be more than 28 plan directives coming from any given plan (that is, no plan can have more than 28 children).
-
There cannot be more than 28 consumer groups in any active plan schema.
-
Plans and consumer groups use the same namespace; therefore, no plan can have the same name as any consumer group.
-
There must be a plan directive for
OTHER_GROUPS
somewhere in any active plan schema.This ensures that a session not covered by the currently active plan is allocated resources as specified by theOTHER_GROUPS
directive.
Note:
These rules are not applicable for CDB resource plans.
If any of the preceding rules are broken when checked by the VALIDATE
or SUBMIT
procedures, then an informative error message is returned. You may then make changes to fix one or more problems and reissue the validate or submit procedures.
157.4.10 CREATE_PLAN Procedure
This procedure creates entries which define resource plans.
Syntax
DBMS_RESOURCE_MANAGER.CREATE_PLAN ( plan IN VARCHAR2, comment IN VARCHAR2 DEFAULT NULL, cpu_mth IN VARCHAR2 DEFAULT NULL, -- deprecated active_sess_pool_mth IN VARCHAR2 DEFAULT 'ACTIVE_SESS_POOL_ABSOLUTE', parallel_degree_limit_mth IN VARCHAR2 DEFAULT 'PARALLEL_DEGREE_LIMIT_ABSOLUTE', queueing_mth IN VARCHAR2 DEFAULT 'FIFO_TIMEOUT', mgmt_mth IN VARCHAR2 DEFAULT 'EMPHASIS', sub_plan IN BOOLEAN DEFAULT FALSE, max_iops IN NUMBER DEFAULT NULL, max_mbps IN NUMBER DEFAULT NULL);
Parameters
Table 157-9 CREATE_PLAN Procedure Parameters
Parameter | Description |
---|---|
|
Name of the resource plan |
|
User comment |
|
Allocation method for CPU resources (deprecated) |
|
Active session pool resource allocation method. Limits the number of active sessions. All other sessions are inactive and wait in a queue to be activated. |
|
Resource allocation method for specifying a limit on the degree of parallelism of any operation. |
|
Queuing resource allocation method. Controls order in which queued inactive sessions will execute. |
|
Resource allocation method for specifying how much resources (for example, CPU or I/O) each consumer group or sub-plan gets
|
|
If |
|
Nonoperative |
|
Nonoperative |
Usage Notes
If you want to use any default resource allocation method, then you do not need to specify it when creating or updating a plan.
157.4.11 CREATE_PLAN_DIRECTIVE Procedure
This procedure creates resource plan directives.
Note:
The parameters max_utilization_limit
and parallel_target_percentage
are deprecated with Oracle Database 11g Release 1 (11.1.0.1), and are replaced by utilization_limit
and parallel_server_limit
.
Syntax
DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE ( plan IN VARCHAR2, group_or_subplan IN VARCHAR2, comment IN VARCHAR2 DEFAULT NULL, cpu_p1 IN NUMBER DEFAULT NULL, -- deprecated cpu_p2 IN NUMBER DEFAULT NULL, -- deprecated cpu_p3 IN NUMBER DEFAULT NULL, -- deprecated cpu_p4 IN NUMBER DEFAULT NULL, -- deprecated cpu_p5 IN NUMBER DEFAULT NULL, -- deprecated cpu_p6 IN NUMBER DEFAULT NULL, -- deprecated cpu_p7 IN NUMBER DEFAULT NULL, -- deprecated cpu_p8 IN NUMBER DEFAULT NULL, -- deprecated active_sess_pool_p1 IN NUMBER DEFAULT NULL, queueing_p1 IN NUMBER DEFAULT NULL, parallel_degree_limit_p1 IN NUMBER DEFAULT NULL, switch_group IN VARCHAR2 DEFAULT NULL, switch_time IN NUMBER DEFAULT NULL, switch_estimate IN BOOLEAN DEFAULT FALSE, max_est_exec_time IN NUMBER DEFAULT NULL, undo_pool IN NUMBER DEFAULT NULL, max_idle_time IN NUMBER DEFAULT NULL, max_idle_blocker_time IN NUMBER DEFAULT NULL, switch_time_in_call IN NUMBER DEFAULT NULL, -- deprecated mgmt_p1 IN NUMBER DEFAULT NULL, mgmt_p2 IN NUMBER DEFAULT NULL, mgmt_p3 IN NUMBER DEFAULT NULL, mgmt_p4 IN NUMBER DEFAULT NULL, mgmt_p5 IN NUMBER DEFAULT NULL, mgmt_p6 IN NUMBER DEFAULT NULL, mgmt_p7 IN NUMBER DEFAULT NULL, mgmt_p8 IN NUMBER DEFAULT NULL, switch_io_megabytes IN NUMBER DEFAULT NULL, switch_io_reqs IN NUMBER DEFAULT NULL, switch_for_call IN BOOLEAN DEFAULT NULL, max_utilization_limit IN NUMBER DEFAULT NULL, -- deprecated parallel_target_percentage IN NUMBER DEFAULT NULL, -- deprecated parallel_server_limit IN NUMBER DEFAULT NULL, utilization_limit IN NUMBER DEFAULT NULL, switch_io_logical IN NUMBER DEFAULT NULL, switch_elapsed_time IN NUMBER DEFAULT NULL, shares IN NUMBER DEFAULT NULL, parallel_stmt_critical IN VARCHAR2 DEFAULT NULL, session_pga_limit IN NUMBER DEFAULT NULL, pq_timeout_action IN NUMBER DEFAULT NULL, parallel_queue_timeout IN NUMBER DEFAULT NULL,);
Note:
Oracle recommends that you use shares
instead of mgmt_p*
.
Parameters
Table 157-10 CREATE_PLAN_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the resource plan |
|
Name of the consumer group or subplan |
|
Comment for the plan directive |
|
-- deprecated: use |
|
-- deprecated: use |
|
-- deprecated: use |
|
-- deprecated: use |
|
-- deprecated: use |
|
-- deprecated: use |
|
-- deprecated: use |
|
-- deprecated: use |
|
Specifies maximum number of sessions that can currently have an active call |
|
Specified time (in seconds) after which a call in the inactive session queue (waiting for execution) will time out. Default is |
|
Specifies a limit on the degree of parallelism for any operation. Default is |
|
Specifies consumer group to switch to, once a switch condition is met. If the group name is |
|
Specifies the time on CPU (not elapsed time) that a session can execute before an action is taken. Default is |
|
If Default value is |
|
Specifies the maximum execution time (in CPU seconds) allowed for a session. If the optimizer estimates that an operation will take longer than |
|
Limits the size in kilobytes of the undo records corresponding to uncommitted transactions by this consumer group |
|
Indicates the maximum session idle time. Default is |
|
Maximum amount of time in seconds that a session can be idle while blocking another session's acquisition of a resource |
|
Deprecated. If this parameter is specified, |
|
Resource allocation value for level 1 (replaces
|
|
Resource allocation value for level 2 (replaces
|
|
Resource allocation value for level 3 (replaces
|
|
Resource allocation value for level 4 (replaces
|
|
Resource allocation value for level 5 (replaces
|
|
Resource allocation value for level 6 (replaces
|
|
Resource allocation value for level 7 (replaces
|
|
Resource allocation value for level 8 (replaces
|
|
Specifies the amount of I/O (in MB) that a session can issue before an action is taken. Default is |
|
Specifies the number of I/O requests that a session can issue before an action is taken. Default is |
|
Specifies that if an action is taken because of the |
|
-- deprecated: use |
|
-- deprecated: use |
|
Specifies the time (in seconds) that a parallel statement may remain in its Consumer Group's parallel statement queue before it is removed and terminated with an error (ORA- 07454). Note: You can use the |
|
Specifies the maximum percentage of |
|
Resource limit. Currently it includes CPU and I/O for Exadata. For CPU, this limits the CPU utilization for the consumer group. For Exadata I/O, this limits the disk utilization for the consumer group. This does not apply to parallel servers. |
|
Number of logical IOs that will trigger the action specified by |
|
Elapsed time that will trigger the action specified by |
|
Specifies the share of resource allocation for the consumer group. CPU Resource Manager and Exadata I/O Resource Manager are enabled by specifying shares for each consumer group. The |
|
If set to If set to Default is |
|
Maximum amount of untunable PGA (in MB) that a session in this consumer group can allocate before being terminated. SQL operations that allocate tunable PGA (operations that can opt to use temp space) are not controlled by this limit. |
|
Specifies the action to be taken when a parallel statement is removed from the queue due to The values are:
The default action of this parameter is |
Usage Notes
-
All parameters default to
NULL
. -
For
max_idle_time
andmax_idle_blocker_time
,PMON
will check these limits once a minute. If it finds a session that has exceeded one of the limits, it will forcibly kill the session and clean up all its state. -
The parameter
switch_for_call
is mostly useful for three-tier applications where the mid-tier server is implementing session pooling. By usingswitch_for_call
, the resource usage of one client will not affect a future client that happens to be executed on the same session. -
An error is thrown if
PQ_TIMEOUT_ACTION
is specified, butPARALLEL_QUEUE_TIMEOUT
is not specified. -
Specifies the action to be taken when a parallel statement is removed from the queue.
157.4.12 CREATE_SIMPLE_PLAN Procedure
This procedure creates a single-level resource plan containing up to eight consumer groups in one step. You do not need to create a pending area manually before creating a resource plan, or use the CREATE_CONSUMER_GROUP
and CREATE_RESOURCE_PLAN_DIRECTIVES
procedures separately.
Syntax
DBMS_RESOURCE_MANAGER.CREATE_SIMPLE_PLAN ( simple_plan IN VARCHAR2 DEFAULT NULL, consumer_group1 IN VARCHAR2 DEFAULT NULL, group1_cpu IN NUMBER DEFAULT NULL, -- deprecated consumer_group2 IN VARCHAR2 DEFAULT NULL, group2_cpu IN NUMBER DEFAULT NULL, -- deprecated consumer_group3 IN VARCHAR2 DEFAULT NULL, group3_cpu IN NUMBER DEFAULT NULL, -- deprecated consumer_group4 IN VARCHAR2 DEFAULT NULL, group4_cpu IN NUMBER DEFAULT NULL, -- deprecated consumer_group5 IN VARCHAR2 DEFAULT NULL, group5_cpu IN NUMBER DEFAULT NULL, -- deprecated consumer_group6 IN VARCHAR2 DEFAULT NULL, group6_cpu IN NUMBER DEFAULT NULL, -- deprecated consumer_group7 IN VARCHAR2 DEFAULT NULL, group7_cpu IN NUMBER DEFAULT NULL, -- deprecated consumer_group8 IN VARCHAR2 DEFAULT NULL, group8_cpu IN NUMBER DEFAULT NULL, -- deprecated group1_percent IN NUMBER DEFAULT NULL, group2_percent IN NUMBER DEFAULT NULL, group3_percent IN NUMBER DEFAULT NULL, group4_percent IN NUMBER DEFAULT NULL, group5_percent IN NUMBER DEFAULT NULL, group6_percent IN NUMBER DEFAULT NULL, group7_percent IN NUMBER DEFAULT NULL, group8_percent IN NUMBER DEFAULT NULL);
Parameters
Table 157-11 CREATE_SIMPLE_PLAN Procedure Parameters
Parameter | Description |
---|---|
|
Name of the resource plan |
|
Name of the consumer group |
|
Percentage for group (deprecated) |
|
Name of the consumer group |
|
Percentage for group (deprecated) |
|
Name of the consumer group |
|
Percentage for group (deprecated) |
|
Name of the consumer group |
|
Percentage for group (deprecated) |
|
Name of the consumer group |
|
Percentage for group (deprecated) |
|
Name of the consumer group |
|
Percentage for group (deprecated) |
|
Name of the consumer group |
|
Percentage for group (deprecated) |
|
|
|
Percentage for group (deprecated) |
|
Percentage of resources allocated for this consumer group |
|
Percentage of resources allocated for this consumer group |
|
Percentage of resources allocated for this consumer group |
|
Percentage of resources allocated for this consumer group |
|
Percentage of resources allocated for this consumer group |
|
Percentage of resources allocated for this consumer group |
|
Percentage of resources allocated for this consumer group |
|
Percentage of resources allocated to other groups |
157.4.13 DELETE_CATEGORY Procedure
This procedure deletes an existing resource consumer group category.
Syntax
DBMS_RESOURCE_MANAGER.DELETE_CATEGORY ( category IN VARCHAR2);
Parameters
Table 157-12 DELETE_CATEGORY Procedure Parameters
Parameter | Description |
---|---|
|
Name of consumer group category |
157.4.14 DELETE_CDB_PLAN Procedure
This procedure deletes the consolidation resource plan.
Syntax
DBMS_RESOURCE_MANAGER.DELETE_CDB_PLAN ( plan IN VARCHAR2(32) DEFAULT NULL);
Parameters
Table 157-13 DELETE_CDB_PLAN Procedure Parameters
Parameter | Description |
---|---|
|
Name of the consolidation plan |
Usage Notes
This procedure can be run only from the CDB root (CDB$ROOT
).
157.4.15 DELETE_CDB_PLAN_DIRECTIVE Procedure
This procedure deletes the plan directives of the consolidation resource plan. Once the plan directive is deleted, the pluggable database will get the default resource allocation.
Syntax
DBMS_RESOURCE_MANAGER.DELETE_CDB_PLAN_DIRECTIVE ( plan IN VARCHAR2(32) DEFAULT NULL, pluggable_database IN VARCHAR2(32) DEFAULT NULL);
Parameters
Table 157-14 DELETE_CDB_PLAN_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the consolidation plan |
|
Name of the pluggable database in which the plan directive is to be deleted |
Usage Notes
This procedure can be run only from the CDB root (CDB$ROOT
).
157.4.16 DELETE_CDB_PROFILE_DIRECTIVE Procedure
This procedure deletes the performance profile directive of the consolidation resource plan. Once the directive is deleted, the pluggable databases (PDBs) that use the performance profile use the default resource allocation.
For a PDB to use a performance profile, the PDB must have the DB_PERFORMANCE_PROFILE
initialization parameter set to the performance profile name.
Syntax
DBMS_RESOURCE_MANAGER.DELETE_CDB_PROFILE_DIRECTIVE ( plan IN VARCHAR2(32) DEFAULT NULL, profile IN VARCHAR2(32) DEFAULT NULL);
Parameters
Table 157-15 DELETE_CDB_PROFILE_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the consolidation plan |
|
Name of the performance profile directive to be deleted |
Usage Notes
This procedure can be run only from the CDB root (CDB$ROOT
).
157.4.17 DELETE_CONSUMER_GROUP Procedure
This procedure deletes entries which define resource consumer groups.
Syntax
DBMS_RESOURCE_MANAGER.DELETE_CONSUMER_GROUP ( consumer_group IN VARCHAR2);
Parameters
Table 157-16 DELETE_CONSUMER_GROUP Procedure Parameters
Parameters | Description |
---|---|
|
Name of the consumer group to be deleted |
157.4.18 DELETE_PLAN Procedure
This procedure deletes the specified plan as well as all the plan directives to which it refers.
Syntax
DBMS_RESOURCE_MANAGER.DELETE_PLAN ( plan IN VARCHAR2);
Parameters
Table 157-17 DELETE_PLAN Procedure Parameters
Parameter | Description |
---|---|
|
Name of the resource plan to delete |
157.4.19 DELETE_PLAN_CASCADE Procedure
This procedure deletes the specified plan and all of its descendants (plan directives, subplans, consumer groups). Mandatory objects and directives are not deleted.
Syntax
DBMS_RESOURCE_MANAGER.DELETE_PLAN_CASCADE ( plan IN VARCHAR2);
Parameters
Table 157-18 DELETE_PLAN_CASCADE Procedure Parameters
Parameters | Description |
---|---|
|
Name of the plan |
Usage Notes
If DELETE_PLAN_CASCADE
encounters any error, then it rolls back the operation, and nothing is deleted.
157.4.20 DELETE_PLAN_DIRECTIVE Procedure
This procedure deletes resource plan directives.
Syntax
DBMS_RESOURCE_MANAGER.DELETE_PLAN_DIRECTIVE ( plan IN VARCHAR2, group_or_subplan IN VARCHAR2);
Parameters
Table 157-19 DELETE_PLAN_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the resource plan |
|
Name of the group or subplan |
157.4.21 DEQUEUE_PARALLEL_STATEMENT Procedure
This procedure dequeues a parallel statement from the parallel statement queue.
If the PARALLEL_DEGREE_POLICY
initialization parameter is set to AUTO
or ADAPTIVE
, then parallel statement queuing is enabled. If a parallel statement is in the parallel statement queue, then you can use this procedure to dequeue the parallel statement so that it runs immediately.
Syntax
DBMS_RESOURCE_MANAGER.DEQUEUE_PARALLEL_STATEMENT ( session_id IN PLS_INTEGER, session_serial IN PLS_INTEGER, inst_id IN PLS_INTEGER DEFAULT NULL, sql_id IN VARCHAR2 DEFAULT NULL);
Parameters
Table 157-20 DEQUEUE_PARALLEL_STATEMENT Procedure Parameters
Parameter | Description |
---|---|
|
The session id of the session running the parallel statement to be dequeued. |
|
The serial number of the session. |
|
Instance ID where the session is running. If |
|
The SQL ID of the session's statement to dequeue. If the session is running SQL with a different SQL ID, then the statement is not dequeued. |
157.4.22 END_SQL_BLOCK Procedure
This procedure, to be used with parallel statement queuing, indicates the end of a block of SQL statements that should be treated as a group by resource manager.
Syntax
DBMS_RESOURCE_MANAGER.END_SQL_BLOCK;
Usage Notes
For more information, see "Parallel Statement Queuing" and "Managing Parallel Statement Queuing with Resource Manager" in Oracle Database VLDB and Partitioning Guide.
157.4.23 SET_CONSUMER_GROUP_MAPPING Procedure
This procedure adds, deletes, or modifies entries that map sessions to consumer groups, based on the session's login and runtime attributes.
Syntax
DBMS_RESOURCE_MANAGER.SET_CONSUMER_GROUP_MAPPING( attribute IN VARCHAR2, value IN VARCHAR2, consumer_group IN VARCHAR2 DEFAULT NULL);
Parameters
Table 157-21 SET_CONSUMER_GROUP_MAPPING Procedure Parameters
Parameters | Description |
---|---|
|
Mapping attribute to add or modify. It can be one of the Constants listed. |
|
Attribute value to match. This includes both absolute mapping and regular expressions. |
|
Name of the mapped consumer group, or |
Usage Notes
-
If no mapping exists for the given attribute and value, a mapping to the given consumer group will be created. If a mapping already exists for the given attribute and value, the mapped consumer group will be updated to the one given. If the
consumer_group
argument isNULL
, then any mapping from the given attribute and value will be deleted. -
The subprogram supports simple regex expressions for the
value
parameter. It implements the same semantics as the SQL'LIKE'
operator. Specifically, it uses'%'
as amulticharacter wildcard and'_'
as a single character wildcard. The'\'
character can be used to escape the wildcards. Note that wildcards can only be used if the attribute is one of the following:-
CLIENT_OS_USER
-
CLIENT_PROGRAM
-
CLIENT_MACHINE
-
MODULE_NAME
-
MODULE_NAME_ACTION
-
SERVICE_MODULE
-
SERVICE_MODULE_ACTION
-
-
Consumer group mapping comparisons for
DBMS_RESOURCE_MANAGER.CLIENT_PROGRAM
are performed by stripping the@
sign and following characters fromV$SESSION.PROGRAM
before comparing it to theCLIENT_PROGRAM
value supplied.
157.4.24 SET_CONSUMER_GROUP_MAPPING_PRI Procedure
Multiple attributes of a session can be used to map the session to a consumer group. This procedure prioritizes the attribute mappings.
Syntax
DBMS_RESOURCE_MANAGER.SET_CONSUMER_GROUP_MAPPING_PRI( explicit IN NUMBER, oracle_user IN NUMBER, service_name IN NUMBER, client_os_user IN NUMBER, client_program IN NUMBER, client_machine IN NUMBER, module_name IN NUMBER, module_name_action IN NUMBER, service_module IN NUMBER, service_module_action IN NUMBER, client_id IN NUMBER DEFAULT 11);
Parameters
Table 157-22 SET_CONSUMER_GROUP_MAPPING_PRI Procedure Parameters
Parameters | Description |
---|---|
|
Priority of the explicit mapping |
|
Priority of the Oracle user name mapping |
|
Priority of the client service name mapping |
|
Priority of the client operating system user name mapping |
|
Priority of the client program mapping |
|
Priority of the client machine mapping |
|
Priority of the application module name mapping |
|
Priority of the application module name and action mapping |
|
Priority of the service name and application module name mapping |
|
Priority of the service name, application module name, and application action mapping |
|
Client identifier |
Usage Notes
-
This procedure requires that you include the pseudo-attribute
explicit
as an argument. It must be set to 1. It indicates that explicit consumer group switches have the highest priority. You explicitly switch consumer groups with these package procedures:-
DBMS_SESSION
.SWITCH_CURRENT_CONSUMER_GROUP
-
DBMS_RESOURCE_MANAGER
.SWITCH_CONSUMER_GROUP_FOR_SESS
-
DBMS_RESOURCE_MANAGER
.SWITCH_CONSUMER_GROUP_FOR_USER
-
-
Each priority value must be a unique integer from 1 to 11. Together, they establish an ordering where 1 is the highest priority and 11 is the lowest.
157.4.25 SET_INITIAL_CONSUMER_GROUP Procedure
This deprecated procedure sets the initial resource consumer group for a user.
The initial consumer group of a user is the consumer group to which any session created by that user initially belongs.
Note:
This procedure is deprecated in Release 11gR1. While the procedure remains available in the package, Initial Consumer Group is set by the session-to-consumer group mapping rules.
Syntax
DBMS_RESOURCE_MANAGER.SET_INITIAL_CONSUMER_GROUP ( user IN VARCHAR2, consumer_group IN VARCHAR2);
Parameters
Table 157-23 SET_INITIAL_CONSUMER_GROUP Procedure Parameters
Parameters | Description |
---|---|
|
Name of the user |
|
User's initial consumer group |
Usage Notes
-
The
ADMINISTER_RESOURCE_MANAGER
or theALTER
USER
system privilege are required to be able to execute this procedure. The user, orPUBLIC
, must be directly granted switch privilege to a consumer group before it can be set to be the user's initial consumer group. Switch privilege for the initial consumer group cannot come from a role granted to that user.Note:
These semantics are similar to those for
ALTER
USER
DEFAULT
ROLE
. -
If the initial consumer group for a user has never been set, then the user's initial consumer group is automatically the consumer group:
DEFAULT_CONSUMER_GROUP
. -
DEFAULT_CONSUMER_GROUP
has switch privileges granted toPUBLIC
; therefore, all users are automatically granted switch privilege for this consumer group. Upon deletion of a consumer group, all users having the deleted group as their initial consumer group now haveDEFAULT_CONSUMER_GROUP
as their initial consumer group. All currently active sessions belonging to a deleted consumer group are switched toDEFAULT_CONSUMER_GROUP
.
157.4.26 SUBMIT_PENDING_AREA Procedure
This procedure submits pending changes for the resource manager. It clears the pending area after validating and committing the changes (if valid).
Note:
A call to SUBMIT_PENDING_AREA
may fail even if VALIDATE_PENDING_AREA
succeeds. This may happen if a plan being deleted is loaded by an instance after a call to VALIDATE_PENDING_AREA
, but before a call to SUBMIT_PENDING_AREA
.
Syntax
DBMS_RESOURCE_MANAGER.SUBMIT_PENDING_AREA;
157.4.27 SWITCH_CONSUMER_GROUP_FOR_SESS Procedure
This procedure changes the resource consumer group of a specific session. It also changes the consumer group of any parallel execution servers that are related to the top user session. This procedure is RAC instance specific. You need to connect to the PDB in same RAC instance where the session to be switched is running, and then run this procedure.
Syntax
DBMS_RESOURCE_MANAGER.SWITCH_CONSUMER_GROUP_FOR_SESS ( session_id IN NUMBER, session_serial IN NUMBER, consumer_group IN VARCHAR2);
Parameters
Table 157-24 SWITCH_CONSUMER_GROUP_FOR_SESS Procedure Parameters
Parameter | Description |
---|---|
|
SID column from the view |
|
|
|
Name of the consumer group to which to switch |
Note:
Specifying a value of'KILL_SESSION'
for the
CONSUMER_GROUP
parameter is not permitted. It will
return error ORA-29366: invalid CONSUMER_GROUP argument
specified
.
157.4.28 SWITCH_CONSUMER_GROUP_FOR_USER Procedure
This procedure changes the resource consumer group for all sessions with a given user ID. It also changes the consumer group of any parallel execution servers that are related to the top user session.
Syntax
DBMS_RESOURCE_MANAGER.SWITCH_CONSUMER_GROUP_FOR_USER ( user IN VARCHAR2, consumer_group IN VARCHAR2);
Parameters
Table 157-25 SWITCH_CONSUMER_GROUP_FOR_USER Procedure Parameters
Parameter | Description |
---|---|
|
Name of the user |
|
Name of the consumer group to which to switch |
Usage Notes
-
The SWITCH_CONSUMER_GROUP_FOR_SESS Procedure and the
SWITCH_CONSUMER_GROUP_FOR_USER
procedures let you raise or lower the allocation of CPU resources of certain sessions or users. This provides a functionality similar to thenice
command on UNIX. -
These procedures cause the session to be moved into the newly specified consumer group immediately.
157.4.29 SWITCH_PLAN Procedure
This procedure sets the current resource manager plan.
Syntax
DBMS_RESOURCE_MANAGER.SWITCH_PLAN( plan_name IN VARCHAR2, sid IN VARCHAR2 DEFAULT '*', allow_scheduler_plan_switches IN BOOLEAN DEFAULT TRUE);
Parameters
Table 157-26 SWITCH_PLAN Procedure Parameters
Parameter | Description |
---|---|
|
Name of the plan to which to switch. Passing in an empty string ('') for the |
|
The |
|
|
157.4.30 UPDATE_CATEGORY Procedure
This procedure updates an existing resource consumer group category.
Syntax
DBMS_RESOURCE_MANAGER.UPDATE_CATEGORY ( category IN VARCHAR2, new_comment IN VARCHAR2 DEFAULT NULL);
Parameters
Table 157-27 UPDATE_CATEGORY Procedure Parameters
Parameter | Description |
---|---|
|
Name of consumer group category |
|
User comment |
Usage Notes
To clear (reset to the directive's default value), use the value -1
.
157.4.31 UPDATE_CDB_AUTOTASK_DIRECTIVE Procedure
This procedure updates the plan directives with regard to automated maintenance tasks in the CDB root (CDB$ROOT
).
By default, all maintenance tasks occur directly in the PDBs themselves.
Syntax
DBMS_RESOURCE_MANAGER.UPDATE_CDB_AUTOTASK_DIRECTIVE ( plan IN VARCHAR2, new_comment IN VARCHAR2 DEFAULT NULL, new_shares IN NUMBER DEFAULT NULL, new_utilization_limit IN NUMBER DEFAULT NULL, new_parallel_server_limit IN NUMBER DEFAULT NULL, new_memory_limit IN NUMBER DEFAULT NULL, new_memory_min IN NUMBER DEFAULT NULL);
Parameters
Table 157-28 UPDATE_CDB_AUTOTASK_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the consolidation plan |
|
New user comment |
|
Specifies the new share of resource allocation for CDB root’s automated maintenance tasks |
|
Specifies the new maximum percentage of CPU that automated maintenance tasks in the CDB root can utilize |
|
Specifies the new maximum percentage of |
|
This parameter is only applicable to Oracle Exadata storage for configuring the Database Smart Flash Cache and PMEM Cache. |
|
This parameter is only applicable to Oracle Exadata storage for configuring the Database Smart Flash Cache and PMEM Cache. |
Usage Notes
-
By default for automated maintenance tasks, the values are
-
shares
:-1
-
utilization_limit
:90
-
parallel_server_limit
:100
-
-
The
shares
=-1
means that the automated maintenance tasks get an allocation of 20% of the system. If the user specifies theshares
, it behaves the same properties as the other CDB plan directive functions. If the user does not change the shares or later changes it back to-1
, autotask will get 20% of the system. -
This procedure can be run only from the CDB root.
-
To clear (reset to the directive's default value), use the value
-1
.
157.4.32 UPDATE_CDB_DEFAULT_DIRECTIVE Procedure
This procedure updates the plan directives of the consolidation resource plan.
Syntax
DBMS_RESOURCE_MANAGER.UPDATE_CDB_DEFAULT_DIRECTIVE ( plan IN VARCHAR2 DEFAULT NULL, new_comment IN VARCHAR2 DEFAULT NULL, new_shares IN NUMBER DEFAULT NULL, new_utilization_limit IN NUMBER DEFAULT NULL, new_parallel_server_limit IN NUMBER DEFAULT NULL, new_memory_limit IN NUMBER DEFAULT NULL, new_memory_min IN NUMBER DEFAULT NULL);
Parameters
Table 157-29 UPDATE_CDB_DEFAULT_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the consolidation plan |
|
New user comment |
|
Specifies the share of resource allocation for the pluggable database. CPU Resource Manager and Exadata I/O Resource Manager are enabled by specifying shares for each PDB. The |
|
Specifies the maximum percentage of CPU that the pluggable database can utilize. |
|
Specifies the maximum percentage of |
|
This parameter is only applicable to Oracle Exadata storage for configuring the Database Smart Flash Cache and PMEM Cache. |
|
This parameter is only applicable to Oracle Exadata storage for configuring the Database Smart Flash Cache and PMEM Cache. |
Usage Notes
-
By default, the default values are
-
new_shares
: 1 -
utilization_limit
: 100 -
parallel_server_limit
: 100
-
-
Note that the default values are
NULL
. This has the same meaning as in UPDATE_CDB_PLAN_DIRECTIVE Procedure. If the user does not specify a value, the value will not be modified. -
This procedure can be run only from the CDB root (
CDB$ROOT
). -
To clear (reset to the directive's default value), use the value
-1
.
157.4.33 UPDATE_CDB_PLAN Procedure
This procedure updates the consolidation resource plan.
Syntax
DBMS_RESOURCE_MANAGER.UPDATE_CDB_PLAN ( plan IN VARCHAR2(32), new_comment IN VARCHAR2(2000) DEFAULT NULL);
Parameters
Table 157-30 UPDATE_CDB_PLAN Procedure Parameters
Parameter | Description |
---|---|
|
Name of the consolidation plan |
|
User comment |
Usage Notes
-
This procedure can be run only from the CDB root (
CDB$ROOT
). -
To clear (reset to the directive's default value), use the value
-1
.
157.4.34 UPDATE_CDB_PLAN_DIRECTIVE Procedure
Updates the plan directives for a consolidation resource plan. Plan directives specify the resource allocation policy for pluggable databases (PDBs).
Syntax
DBMS_RESOURCE_MANAGER.UPDATE_CDB_PLAN_DIRECTIVE ( plan IN VARCHAR2 (30), pluggable_database IN VARCHAR2 (30) new_comment IN VARCHAR2 (200) DEFAULT NULL, new_shares IN NUMBER DEFAULT NULL, new_utilization_limit IN NUMBER DEFAULT NULL, new_parallel_server_limit IN NUMBER DEFAULT NULL, new_memory_limit IN NUMBER DEFAULT NULL, new_memory_min IN NUMBER DEFAULT NULL);
Parameters
Table 157-31 UPDATE_CDB_PLAN_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the consolidation plan |
|
Name of the pluggable database |
|
New user comment |
|
The share of resource allocation for the pluggable database CPU Resource Manager is enabled by specifying shares for each PDB. The |
|
The new maximum percentage of CPU that the pluggable database can utilize |
|
The new maximum percentage of |
|
This parameter is only applicable to Oracle Exadata storage for configuring the Database Smart Flash Cache and PMEM Cache. |
|
This parameter is only applicable to Oracle Exadata storage for configuring the Database Smart Flash Cache and PMEM Cache. |
Usage Notes
-
The default value for the
new_*
parameters isNULL
which indicates that the existing value is left unchanged. If the user does not specify one of the arguments when calling this function, the value is not modified. -
This procedure can be run only from the CDB root (
CDB$ROOT
). -
To clear (reset to the directive's default value), use the value
-1
.
157.4.35 UPDATE_CDB_PROFILE_DIRECTIVE Procedure
This procedure updates the performance profile directives of the consolidation resource plan. The directives specify the resource allocation policy for pluggable databases (PDBs) that use the performance profile.
For a PDB to use a performance profile, the PDB must have the DB_PERFORMANCE_PROFILE
initialization parameter set to the performance profile name.
Syntax
DBMS_RESOURCE_MANAGER.UPDATE_CDB_PROFILE_DIRECTIVE ( plan IN VARCHAR2, profile IN VARCHAR2, new_comment IN VARCHAR2 (2000) DEFAULT '', new_shares IN NUMBER DEFAULT NULL, new_utilization_limit IN NUMBER DEFAULT NULL, new_parallel_server_limit IN NUMBER DEFAULT NULL, new_memory_limit IN NUMBER DEFAULT 100, new_memory_min IN NUMBER DEFAULT 0);
Parameters
Table 157-32 UPDATE_CDB_PROFILE_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the consolidation plan |
|
Name of the performance profile |
|
New user comment |
|
The share of resource allocation for the PDBs that use the performance profile |
|
The new maximum percentage of CPU that PDBs that use the performance profile can use |
|
The new maximum percentage of |
|
This parameter is only applicable to Oracle Exadata storage for configuring the Database Smart Flash Cache and PMEM Cache. |
|
This parameter is only applicable to Oracle Exadata storage for configuring the Database Smart Flash Cache and PMEM Cache. |
Usage Notes
-
This procedure can be run only from the CDB root (
CDB$ROOT
). -
To clear (reset to the directive's default value), use the value
-1
.
157.4.36 UPDATE_CONSUMER_GROUP Procedure
This procedure updates entries which define resource consumer groups.
Syntax
DBMS_RESOURCE_MANAGER.UPDATE_CONSUMER_GROUP ( consumer_group IN VARCHAR2, new_comment IN VARCHAR2 DEFAULT NULL, new_cpu_mth IN VARCHAR2 DEFAULT NULL, new_mgmt_mth IN VARCHAR2 DEFAULT NULL, new_category IN VARCHAR2 DEFAULT NULL);
Parameters
Table 157-33 UPDATE_CONSUMER_GROUP Procedure Parameter
Parameter | Description |
---|---|
|
Name of consumer group |
|
New user comment |
|
Name of new method for CPU resource allocation (deprecated) |
|
Name of new method for CPU resource allocation |
|
New consumer group category |
Usage Notes
-
If the parameters to the
UPDATE_CONSUMER_GROUP
procedure are not specified, then they remain unchanged in the data dictionary. -
To clear (reset to the directive's default value), use the value
-1
.
157.4.37 UPDATE_PLAN Procedure
This procedure updates entries which define resource plans.
Syntax
DBMS_RESOURCE_MANAGER.UPDATE_PLAN ( plan IN VARCHAR2, new_comment IN VARCHAR2 DEFAULT NULL, new_cpu_mth IN VARCHAR2 DEFAULT NULL, -- deprecated new_active_sess_pool_mth IN VARCHAR2 DEFAULT NULL, new_parallel_degree_limit_mth IN VARCHAR2 DEFAULT NULL, new_queueing_mth IN VARCHAR2 DEFAULT NULL, new_mgmt_mth IN VARCHAR2 DEFAULT NULL, new_sub_plan IN BOOLEAN DEFAULT FALSE, new_max_iops IN NUMBER DEFAULT NULL, new_max_mbps IN NUMBER DEFAULT NULL);
Parameters
Table 157-34 UPDATE_PLAN Procedure Parameters
Parameter | Description |
---|---|
|
Name of resource plan |
|
New user comment |
|
Name of new allocation method for CPU resources (deprecated) |
|
Name of new method for maximum active sessions |
|
Name of new method for degree of parallelism |
|
Specifies type of queuing policy to use with active session pool feature |
|
Resource allocation method for specifying how much resources (for example, CPU or I/O) each consumer group or sub-plan gets
|
|
New setting for whether the plan is only intended for use as a sub-plan |
|
Nonoperative |
|
Nonoperative |
Usage Notes
-
If the parameters to UPDATE_PLAN Procedure are not specified, then they remain unchanged in the data dictionary.
-
If you want to use any default resource allocation method, then you do not need to specify it when creating or updating a plan.
-
To clear (reset to the directive's default value), use the value
-1
.
157.4.38 UPDATE_PLAN_DIRECTIVE Procedure
This procedure updates resource plan directives.
Note:
The parameters new_max_utilization_limit
and new_parallel_target_percentage
are deprecated with Oracle Database 11g Release 1 (12.1.0.1), and are replaced by new_utilization_limit
and new_parallel_server_limit
.
Syntax
DBMS_RESOURCE_MANAGER.UPDATE_PLAN_DIRECTIVE ( plan IN VARCHAR2, group_or_subplan IN VARCHAR2, new_comment IN VARCHAR2 DEFAULT NULL, new_cpu_p1 IN NUMBER DEFAULT NULL, -- deprecated new_cpu_p2 IN NUMBER DEFAULT NULL, -- deprecated new_cpu_p3 IN NUMBER DEFAULT NULL, -- deprecated new_cpu_p4 IN NUMBER DEFAULT NULL, -- deprecated new_cpu_p5 IN NUMBER DEFAULT NULL, -- deprecated new_cpu_p6 IN NUMBER DEFAULT NULL, -- deprecated new_cpu_p7 IN NUMBER DEFAULT NULL, -- deprecated new_cpu_p8 IN NUMBER DEFAULT NULL, -- deprecated new_active_sess_pool_p1 IN NUMBER DEFAULT NULL, new_queueing_p1 IN NUMBER DEFAULT NULL, new_parallel_degree_limit_p1 IN NUMBER DEFAULT NULL, new_switch_group IN VARCHAR2 DEFAULT NULL, new_switch_time IN NUMBER DEFAULT NULL, new_switch_estimate IN BOOLEAN DEFAULT FALSE, new_max_est_exec_time IN NUMBER DEFAULT NULL, new_undo_pool IN NUMBER DEFAULT NULL, new_max_idle_time IN NUMBER DEFAULT NULL, new_max_idle_blocker_time IN NUMBER DEFAULT NULL, switch_time_in_call IN NUMBER DEFAULT NULL, -- deprecated new_mgmt_p1 IN NUMBER DEFAULT NULL, new_mgmt_p2 IN NUMBER DEFAULT NULL, new_mgmt_p3 IN NUMBER DEFAULT NULL, new_mgmt_p4 IN NUMBER DEFAULT NULL, new_mgmt_p5 IN NUMBER DEFAULT NULL, new_mgmt_p6 IN NUMBER DEFAULT NULL, new_mgmt_p7 IN NUMBER DEFAULT NULL, new_mgmt_p8 IN NUMBER DEFAULT NULL, new_switch_io_megabytes IN NUMBER DEFAULT NULL, new_switch_io_reqs IN NUMBER DEFAULT NULL, new_switch_for_call IN BOOLEAN DEFAULT NULL, new_max_utilization_limit IN NUMBER DEFAULT NULL, new_parallel_target_percentage IN NUMBER DEFAULT NULL, new_parallel_queue_timeout IN NUMBER DEFAULT NULL, new_parallel_server_limit IN NUMBER DEFAULT NULL, new_utilization_limit IN NUMBER DEFAULT NULL, new_switch_io_logical IN NUMBER DEFAULT NULL, new_switch_elapsed_time IN NUMBER DEFAULT NULL, new_shares IN NUMBER DEFAULT NULL, new_parallel_stmt_critical IN VARCHAR2 DEFAULT NULL, new_session_pga_limit IN NUMBER DEFAULT NULL, new_pq_timeout_action IN NUMBER DEFAULT NULL);
Parameters
Table 157-35 UPDATE_PLAN_DIRECTIVE Procedure Parameters
Parameter | Description |
---|---|
|
Name of the resource plan |
|
Name of the consumer group or subplan |
|
Comment for the plan directive |
|
Deprecated - use |
|
Deprecated - use |
|
Deprecated - use |
|
Deprecated- use |
|
Deprecated - use |
|
Deprecated- use |
|
Deprecated- use |
|
Deprecated- use |
|
Specifies maximum number of concurrently active sessions for a consumer group. Default is |
|
Specified time (in seconds) after which a job in the inactive session queue (waiting for execution) will time out. Default is |
|
Specifies a limit on the degree of parallelism for any operation. Default is |
|
Specifies consumer group to which this session is switched if other switch criteria are met. Default is |
|
Specifies time (in CPU seconds) that a session can execute before an action is taken. Default is |
|
If |
|
Specifies the maximum execution time (in CPU seconds) allowed for a session. If the optimizer estimates that an operation will take longer than |
|
Limits the size in kilobytes of the undo records corresponding to uncommitted transactions by this consumer group |
|
Indicates the maximum session idle time. Default is |
|
Maximum amount of time in seconds that a session can be idle while blocking another session's acquisition of a resource |
|
Deprecated. If this parameter is specified, |
|
Resource allocation value for level 1 (replaces
|
|
Resource allocation value for level 2 (replaces
|
|
Resource allocation value for level 3 (replaces
|
|
Resource allocation value for level 4 (replaces
|
|
Resource allocation value for level 5 (replaces
|
|
Resource allocation value for level 6 (replaces
|
|
Resource allocation value for level 7 (replaces
|
|
Resource allocation value for level 8 (replaces
|
|
Specifies the amount of I/O (in MB) that a session can issue before an action is taken. Default is |
|
Specifies the number of I/O requests that a session can issue before an action is taken. Default is |
|
Specifies that if an action is taken because of the |
|
Deprecated - use |
|
Deprecated - use |
|
Parallel server limit. Setting this overwrites the limit for parallel server set by |
|
Resource limit. For CPU, this limits the CPU utilization for the consumer group. For parallel servers, this limits the parallel servers used as a percentage of |
|
Elapsed time that will trigger the action specified by |
|
Specifies the share of resource allocation for the pluggable database. CPU Resource Manager and Exadata I/O Resource Manager are enabled by specifying shares for each PDB. The |
|
If set to If set to Default is |
|
Maximum amount of PGA in MB that sessions in this consumer group can allocate before being terminated. |
|
Specifies the time (in seconds) that a parallel statement may remain in its Consumer Group's parallel statement queue before it is removed. The default action of this parameter is |
|
Specifies the action to be taken when a parallel statement is removed from the queue due to The values are:
|
Usage Notes
-
If the parameters for
UPDATE_PLAN_DIRECTIVE
are left unspecified, then they remain unchanged in the data dictionary. -
For
new_max_idle_time
andnew_max_idle_blocker_time
,PMON
will check these limits once a minute. If it finds a session that has exceeded one of the limits, it will forcibly kill the session and clean up all its state. -
The parameter
new_switch_time_in_call
is mostly useful for three-tier applications where the mid-tier server is implementing session pooling. By turning onnew_switch_time_in_call
, the resource usage of one client will not affect the consumer group of a future client that happens to be executed on the same session. -
To clear (reset to the directive's default value), use the value
-1
.