This chapter provides a description of each management template view and its columns. It contains the following sections:
For examples of how to use views, see Examples.
The MGMT$TEMPLATES views displays details of all the management templates stored in the Management Repository.
Table 11-1 MGMT$TEMPLATES
Column | Description |
---|---|
TARGET_TYPE |
The target type defines the set of metrics and policies that are applicable for the target |
TEMPLATE_NAME |
The name of the template |
TEMPLATE_GUID |
The unique global identifier for the template |
DESCRIPTION |
The description of the template |
OWNER |
Enterprise Manager administrator who owns the template |
IS_PUBLIC |
The flag to specify whether the template is accessible to all EM administrators |
CREATED_DATE |
The date or time when the template is created in the repository |
LAST_UPDATED_DATE |
The date or time when the template was last modified in the repository |
LAST_UPDATED_BY |
The Enterprise Manager administrator who last updated the template |
The MGMT$TEMPLATE_POLICY_SETTINGS view displays policy settings for management templates.
Table 11-2 MGMT$TEMPLATE_POLICY_SETTINGS
Column | Description |
---|---|
TARGET_TYPE |
The target type defines the set of metrics and policies that are applicable for the target |
TEMPLATE_NAME |
The name of the template |
TEMPLATE_GUID |
The unique global identifier for the template |
POLICY_NAME |
The name of the policy that is associated with the template |
POLICY_GUID |
The unique global identifier for the policy |
CATEGORY |
The name of the category the policy Refer to MGMT$METRIC_CATEGORIES for the list of all categories |
KEY_VALUE |
The key value for which the alert has been recorded. For composite keys, this is the first part of the key |
KEY_VALUE2 |
For composite keys, this is the second part of the key for which the alert has been recorded |
KEY_VALUE3 |
For composite keys, this is the third part of the key for which the alert has been recorded |
KEY_VALUE4 |
For composite keys, this is the fourth part of the key for which the alert has been recorded |
KEY_VALUE5 |
For composite keys, this is the fifth part of the key for which the alert has been recorded |
KEY_OPERATOR |
Specifies whether the key_value columns have any SQL wildcards. For single key column metrics, the value is 1 if the key_value has wildcard characters, 0 otherwise. For metrics with multiple keys, a list of operators for all key columns will be stored here. For example, a metric with 3 keys (k1, k2, k3) where K1 and K2 use wildcards and K3 uses exact match, then 011 is stored in this column |
PARAMETER_NAME |
The name of the parameter |
PREVENT_OVERRIDE |
The is a flag that specifies that the metric rows with this key_value has a template override flag. Once the template override flag is ON, any template application will not update the threshold/parameter values. |
POLICY_THRESHOLD |
The threshold value configured for the policy parameter |
ACTION_TYPE |
The corrective action type configured. Possible values are: No-Action: when no action is configured Corrective-Action: when a repository side corrective action is configured Agent-Fixit Job: when an Agent side fix-it job is configured. |
ACTION_JOB_TYPE |
Specifies the job type of the corrective action when ACTION_TYPE is “Corrective-Action" |
ACTION_JOB_NAME |
Specifies the job name of the corrective action when ACTION_TYPE is “Corrective-Action" |
ACTION_JOB_OWNER |
Specifies the job owner of the corrective action when ACTION_TYPE is “Corrective-Action" |
The MGMT$TEMPLATE_METRICCOLLECTIONS view displays information on the metric collections defined for a template.
Table 11-3 MGMT$TEMPLATE_METRICCOLLECTION
Column | Description |
---|---|
TEMPLATE_NAME |
The name of the template |
TARGET_TYPE |
The target type defines the set of metrics and policies that are applicable for the target |
TEMPLATE_GUID |
The unique global identifier for the template |
METRIC_NAME |
The name of the metric for which the template collection is configured |
METRIC_COLUMN |
The name of the metric column for which the template collection is configured |
METRIC_GUID |
The unique global identifier for the metric column |
COLLECTION_NAME |
The name of the collection |
IS_REPOSITORY |
Indicates whether this is a repository-side collection. A repository-side collection has a PL/SQL evaluation procedure that is responsible for calculating the metric values. |
FREQUENCY_CODE |
The metric collection frequency type. Possible values are:
|
COLLECTION_FREQUENCY |
The frequency of the metric collection. Value displayed is dependent on the frequency code:
|
UPLOAD_POLICY |
The frequency with which the metric data is uploaded/stored. |
The MGMT$TEMPLATE_METRIC_SETTINGS view displays management template settings.
Table 11-4 MGMT$TEMPLATE_METRIC_SETTINGS
Column | Description |
---|---|
TEMPLATE_NAME |
The name of the template |
TARGET_TYPE |
The target type defines the set of metrics and policies that are applicable for the target |
TEMPLATE_GUID |
The unique global identifier for the template |
METRIC_NAME |
The name of the metric for which the template collection is configured |
METRIC_COLUMN |
The name of the metric column for which the template collection is configured |
METRIC_GUID |
The unique global identifier for the metric column |
COLLECTION_NAME |
The name of the collection |
CATEGORY |
The name of the category the policy. Refer to MGMT$METRIC_CATEGORIES for the list of all categories. |
KEY_VALUE |
The key value for which the alert has been recorded. For composite keys, this is the first part of the key. |
KEY_VALUE2 |
For composite keys, this is the second part of the key for which the alert has been recorded |
KEY_VALUE3 |
For composite keys, this is the third part of the key for which the alert has been recorded |
KEY_VALUE4 |
For composite keys, this is the fourth part of the key for which the alert has been recorded |
KEY_VALUE5 |
For composite keys, this is the fifth part of the key for which the alert has been recorded |
KEY_OPERATOR |
Specifies whether the key_value columns have any SQL wildcards. For single key column metrics, the value is 1 if the key_value has wildcard characters, 0 otherwise. For metrics with multiple keys, a list of operators for all key columns will be stored here. For example, a metric with 3 keys (k1, k2, k3) where K1 and K2 use wildcards and K3 uses exact match, then 011 is stored in this column |
PREVENT_OVERRIDE |
The is a flag that specifies that the metric rows with this key_value has a template override flag. Once the template override flag is ON, any template application will not update the threshold/parameter values. |
WARNING_OPERATOR |
Defines the warning threshold condition to be applied
|
WARNING_THRESHOLD |
The value of the warning threshold |
CRITICAL_OPERATOR |
Defines the critical threshold condition to be applied
|
CRITICAL_THRESHOLD |
The value of the critical threshold |
OCCURRENCE_COUNT |
The number of times the test has to trigger to raise a violation |
WARNING_ACTION_TYPE |
The warning corrective action type configured. Possible values are:
|
WARNING_ACTION_JOB_TYPE |
Specifies the job type of the warning corrective action when WARNING_ACTION_TYPE is “Corrective-Action" |
WARNING_ACTION_JOB_OWNER |
Specifies the job owner of the warning corrective action when WARNING_ACTION_TYPE is “Corrective-Action" |
WARNING_ACTION_JOB_NAME |
Specifies the job name of the warning corrective action when WARNING_ACTION_TYPE is “Corrective-Action" |
CRITICAL_ACTION_TYPE |
The critical corrective action type configured. Possible values are:
|
CRITICAL_ACTION_JOB_TYPE |
Specifies the job type of the critical corrective action when CRITICAL_ACTION_TYPE is “Corrective-Action" |
CRITICAL_ACTION_JOB_OWNER |
Specifies the job owner of the critical corrective action when CRITICAL_ACTION_TYPE is “Corrective-Action" |
CRITICAL_ACTION_JOB_NAME |
Specifies the job name of the critical corrective action when CRITICAL_ACTION_TYPE is “Corrective-Action" |