Database Reference
In-Depth Information
Step 7.4 Resource Plans
To ensure that critical applications such as TAPS and TICKS can obtain sufficient resources from the Oracle resource
pool, the ODRM functionality supports definition of resource plans where applications can be assigned resource
limits such as % of CPU that would be available and so forth. The resource plan is created using the following PL/SQL
definition (or through OEM):
BEGIN
DBMS_RESOURCE_MANAGER.CREATE_PLAN (PLAN=>'SSKY_SCDB_PLAN',
COMMENT=>'high priority plan');
END;
/
BEGIN
DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE
(PLAN =>'SSKY_SCDB_PLAN',
GROUP_OR_SUBPLAN => 'HIGH_PRIORITY',
COMMENT => 'High priority group ',
MGMT_P1 => 50,
PARALLEL_DEGREE_LIMIT_P1 => 4,
ACTIVE_SESS_POOL_P1 => 4);
DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE
(PLAN =>'SSKY_SCDB_PLAN',
GROUP_OR_SUBPLAN => 'STD_PRIORITY',
COMMENT => ' ',
MGMT_P1 => 25);
DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE
(PLAN =>'SSKY_SCDB_PLAN',
GROUP_OR_SUBPLAN => 'LOW_PRIORITY',
COMMENT => ' ',
MGMT_P1 => 15);
DBMS_RESOURCE_MANAGER.CREATE_PLAN_DIRECTIVE
(PLAN =>'SSKY_SCDB_PLAN',
GROUP_OR_SUBPLAN => 'OTHER_GROUPS',
COMMENT => 'common catch all group',
MGMT_P1 => 10);
END;
/
Step 7.5
Once the consumer group definitions have been verified, the next step is to save and enable these definitions using
the following procedure:
BEGIN
DBMS_RESOURCE_MANAGER.VALIDATE_PENDING_AREA();
END;
/
BEGIN
DBMS_RESOURCE_MANAGER.SUBMIT_PENDING_AREA ();
END;
/
 
Search WWH ::




Custom Search