The DBMS_AUTO_TASK_ADMIN
package provides an interface to AUTOTASK
functionality. It is used by the DBA as well as Enterprise Manager to access the AUTOTASK
controls. Enterprise Manager also uses the AUTOTASK
Advisor.
See Also:
Oracle Database Administrator's Guide for more information about "Configuring Automated Maintenance Task"This chapter contains the following sections:
The DBMS_AUTO_TASK_ADMIN
package uses the constants shown in Table 29-1:
Table 29-1 DBMS_AUTO_TASK_ADMIN Constants
Name | Type | Value | Description |
---|---|---|---|
|
|
|
Task with this priority should be executed as time permits |
|
|
|
Task with this priority should be executed within the current Maintenance Window |
|
|
|
Task with this priority is to be executed at the earliest opportunity |
Table 29-2 DBMS_XMLSTORE Package Subprograms
Method | Description |
---|---|
Prevents |
|
Allows a previously disabled client, operation, target type, or individual target to be enabled under |
|
Returns values of select client attributes |
|
Returns percent of resources allocated to each |
|
Manually overrides task priority. |
|
Associates an |
|
Sets percentage-based resource allocation for each High Priority Consumer Group used by |
This procedure prevents AUTOTASK
from executing any requests from a specified client or operation.
Disables all AUTOTASK
functionality.
DBMS_AUTO_TASK_ADMIN.DISABLE;
Disables all tasks for the client or operation.
DBMS_AUTO_TASK_ADMIN.DISABLE ( client_name IN VARCHAR2, operation IN VARCHAR2, window_name IN VARCHAR2);
This procedure allows a previously disabled client, operation, target type, or individual target to be enabled under AUTOTASK
control. Specifying the DEFERRED
option postpones the effect of the call until the start of the next maintenance window. If IMMEDIATE
option is specified the effect of this call is immediate – as long as there is a currently open maintenance window.
Re-enabling AUTOTASK
. This version enables the specified client. Note that any explicitly disabled tasks or operations must be re-enabled individually.
DBMS_AUTO_TASK_ADMIN.ENABLE;
Re-enabling a client or operation.Note that any explicitly disabled tasks or operations must be re-enabled individually.
DBMS_AUTO_TASK_ADMIN.ENABLE ( client_name IN VARCHAR2, operation IN VARCHAR2, window_name IN VARCHAR2);
This procedure returns values of select client attributes.
DBMS_AUTO_TASK_ADMIN.GET_CLIENT_ATTRIBUTES( client_name IN VARCHAR2, service_name OUT VARCHAR2, window_group OUT VARCHAR2);
This procedure returns percent of resources allocated to each AUTOTASK
High Priority Consumer Group.
DBMS_AUTO_TASK_ADMIN.GET_P1_RESOURCES( stats_group_pct OUT NUMBER, seg_group_pct OUT NUMBER, tune_group_pct OUT NUMBER, health_group_pct OUT NUMBER);
This procedure is used to manually override task priority. This can be done at the client, operation or individual task level. This priority assignment is honored during the next maintenance window in which the named client is active. Specifically, setting the priority to URGENT
causes a high priority job to be generated at the start of the maintenance window. Setting priority
to CLEAR
removes the override.
Override Priority for a Client.
DBMS_AUTO_TASK_ADMIN.OVERRIDE_PRIORITY ( client_name IN VARCHAR2, priority IN VARCHAR2);
Override Priority for an Operation.
DBMS_AUTO_TASK_ADMIN.OVERRIDE_PRIORITY ( client_name IN VARCHAR2, operation IN VARCHAR2, priority IN VARCHAR2);
Override Priority for a Task.
DBMS_AUTO_TASK_ADMIN.OVERRIDE_PRIORITY ( client_name IN VARCHAR2, operation IN VARCHAR2, task_target_type IN VARCHAR2, task_target_name IN VARCHAR2, priority IN VARCHAR2);
Table 29-7 OVERRIDE_PRIORITY Procedure Parameters
Parameter | Description |
---|---|
|
Name of the client, as found in |
|
|
|
Name of the operation as specified in |
|
Type of target to be affected, as found in V$ |
|
Name of the specific target to be affected |